Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description still adds real value by flagging irreversible content removal and advising a backup/match confirmation. It omits specifics such as what happens when multiple paragraphs match and the 'all' default resolves to true -- a meaningful gap for a destructive call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the action and scope front-loaded and the caution trailing. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full annotation coverage, the description does not need to explain return values, and it correctly focuses on the destructive-caution angle. It leaves the create/output parameters unexplained at the description level, which is slightly confusing for a delete tool, but the schema resolves that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with six documented parameters, so the schema carries the semantics. The description only echoes 'matching requested text' and 'specified document', adding no syntax, matching-rule, or interaction detail (e.g. how 'all' vs 'search' interact) beyond what the schema already states. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('delete') on a specific resource ('one or more paragraphs matching requested text') within a bounded scope ('a specified local word-processing document'). That is far more precise than the title alone, though it never names the adjacent paragraph tools (document_replace, document_append_paragraph, document_insert_paragraph_before/after) to draw the boundary explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this to delete...' plus 'confirm the exact match and backup needs' gives clear operating context and a pre-flight caution before a destructive call. It stops short of explicit exclusions or alternatives -- it does not say, for example, to use document_replace when the intent is substitution rather than removal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.