docs_delete_paragraph

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

With no annotations, the description carries full burden. It explicitly discloses case-insensitive matching, the behavior that ALL containing paragraphs are deleted, and that a unique match deletes only one. These are non-obvious behavioral traits that materially affect invocation.

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 concise sentences, no fluff. The core action is front-loaded and the behavioral nuances are presented directly.

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?

The tool is simple with only two required params, both fully covered by schema. The description addresses its key behavioral edge cases, and an output schema exists to document return values. Nothing essential is missing for an agent to call it correctly.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining that 'anchor' is a search string with case-insensitive substring matching, which is more specific than the schema's 'Text to search for'. It does not add format constraints, but it clarifies matching rule.

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 a specific action (delete) and a specific resource (paragraphs containing anchor text). It distinguishes from sibling comment and search tools, making the tool's purpose unmistakable.

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?

The behavior description implies usage contexts (delete all matching paragraphs, case-insensitively), but there is no explicit guidance on when to choose this tool over alternatives such as docs_search_replace or docs_delete_comment. It provides enough context for an agent to infer, but not clear exclusions.

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