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

Annotations only declare destructiveHint=true; the description goes well beyond that by disclosing that stored messages are deleted along with the form, that the on-page HTML form stops working, and that the page markup must be cleaned up manually. That is exactly the additional behavioral context an agent needs before an irreversible 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?

Three short declarative sentences, no filler, with the primary action front-loaded and the destructive side effects following immediately. Every sentence carries information.

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 two-parameter destructive tool with annotations covering the safety profile and no output schema required, the description supplies the critical missing context: message loss and the manual page-cleanup step. Nothing essential for calling it correctly is absent.

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 50% – only 'name' is documented, while 'site' has no schema description. The description implicitly conveys both inputs (a form name acted on within a site) but adds no format, syntax, or lookup guidance, so it neither compensates for the gap nor falls below the baseline.

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?

States a precise verb and resource ("Remove a contact form from a site") and the scope of what is affected. It is easily distinguished from set_form/list_forms/form_messages by resource and verb, but no sibling is named or explicitly contrasted, so it falls just short of the top band.

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?

Usage is implied by the destructive framing (use it to delete a form and its messages), but there is no explicit when-to-use vs. when-not guidance and no mention of alternatives such as set_form or form_messages. The agent must infer the calling context.

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