Why the prompt is deliberately plain

The permission prompt is deliberately literal rather than summarized or paraphrased. For a file write, you see the actual target path and the actual size of what is being written. For a shell command, you see the literal command exactly as it will run.

This matters most for bash specifically, since a shell command's real behavior is defined entirely by its literal text; any summary of intent could, in principle, differ from what the command actually executes, and that gap is exactly what a plain, unabbreviated prompt closes.

This same principle, showing the real thing rather than a description of it, is why the transcript covered in Outputs also shows literal commands and literal file paths throughout, not paraphrased summaries.

A plain, literal prompt also avoids a subtle failure mode a summarized one would be vulnerable to: a paraphrase written by the same system proposing the action has an inherent conflict of interest in how charitably it describes that action, however unintentional. Showing the raw text sidesteps the question entirely.

This does mean a long or complex shell command can produce a correspondingly long prompt to read; that is treated as an acceptable tradeoff against showing an abbreviated version that could omit exactly the detail that mattered.