Delete Paragraph

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

The description adds nothing beyond the destructiveHint annotation. It doesn't mention irreversibility, permissions, or error handling. The annotation already signals destructiveness, so the description should provide additional behavioral context.

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?

The description is a single sentence, very concise, but it compromises informativeness. It could be slightly longer to add value without being verbose.

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?

For a simple destructive tool with two required params and no output schema, the description is incomplete. It lacks information about return values, error conditions, and permanent effects.

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?

Input schema has 0% description coverage, and the description does not explain what filename or paragraph_index mean (e.g., file path conventions, 0-indexed vs 1-indexed). No parameter guidance is provided.

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 clearly states it deletes a paragraph from a document, using a specific verb and resource. It distinguishes from siblings like delete_footnote_from_document and add_paragraph, though it doesn't explicitly call out alternatives.

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?

No guidance on when to use this tool versus alternatives (e.g., replace_paragraph_block_below_header) or prerequisites (e.g., document must exist, valid index). The description provides no contextual usage direction.

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