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

The description adds substantial behavioral context beyond the annotations: the deletion is permanent, it removes the form and its PDFs, dry_run has no side effects, and the rehearsal response reports whether the real call would succeed or be refused, its cost, and what rehearsal cannot check. This is consistent with destructiveHint=true and readOnlyHint=false.

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 front-loaded with the permanent deletion behavior and then explains the dry_run path. It is appropriately sized, though the final sentence packs several output-related points together and could be slightly tighter.

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 destructive delete tool with an output schema and destructive annotations, the description covers the key deletion scope and rehearsal semantics well. It leaves minor gaps around permissions, prerequisites, and the exact treatment of attachments or related records, but an agent has enough to invoke 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 description coverage is 0%, so the description must carry parameter meaning. It explains dry_run thoroughly, including side-effect behavior and response meaning, but says nothing about form_id beyond the implied form reference; the schema example shows a UUID but the description does not add further semantics for that required parameter.

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 and resource: it permanently removes a form and its PDFs from the user's library. That is clear enough to distinguish it from most siblings, but it does not explicitly differentiate it from delete_pages or other deletion-adjacent tools.

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?

It clearly explains how to use dry_run=true as a rehearsal, including that nothing is stored, charged, sent, or AI-processed. However, it does not explicitly state when to choose delete_form over alternatives such as delete_pages, nor does it give prerequisites or exclusions.

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