delete_paragraph

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

Lacking annotations, the description only states the core destructive action. It does not disclose consequences like content removal, numbering updates, or error conditions (e.g., if paragraph is read-only or in a tracked changes mode).

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 extremely concise: two sentences with no wasted words. The core action is stated first, and the parameter is explained in a clear list format.

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?

Given the existence of an output schema and the tool's simplicity, the description still lacks important context like error handling, requirements (e.g., document must be open), and behavioral side effects. It feels under-specified for a deletion operation.

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?

With 0% schema description coverage, the description bears the full burden. It explains para_id as 'paraId of the paragraph to remove', which adds minimal value beyond the parameter name. The slight inconsistency (paraId vs para_id) further reduces clarity.

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 the action 'Delete' and the resource 'paragraph' with a specific identifier (paraId). It is unambiguous and distinguishes from sibling tools like delete_text or delete_table_row.

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 is provided on when to use this tool versus alternatives (e.g., delete_text). It does not mention prerequisites, document state, or edge cases.

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