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

Annotations already declare destructiveHint=true and idempotentHint=true; the description goes beyond them by explaining the consequence of the mutation — a form with zero recipients emails nobody while submissions still land in the Forms inbox. That is genuinely useful behavioral context not present in structured fields.

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 short sentences, front-loaded with the action, followed by one high-value consequence. Nothing is wasted and nothing is buried.

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, non-read-only mutation with three undocumented required parameters and no output schema, the description covers the outcome but not the inputs or failure modes. It is adequate to understand what the tool does, not to call it correctly on the first try.

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% for three required parameters (websiteId, formName, recipientId), so the description carries the full burden and largely fails. 'An address for one form' loosely gestures at recipientId and formName, but websiteId is never mentioned and no format or discovery path for recipientId is given.

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 specific verb and resource ('Stops emailing an address for one form'), which cleanly separates it from websiteForms_recipients_add and recipients_resend. It does not name those siblings explicitly, but the effect is unambiguous.

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 verb — call this when you no longer want a given address notified for a form. There is no explicit guidance on when not to use it, no note that the recipientId must already be listed (e.g., via websiteForms_list), and no mention of what happens if the id is unknown.

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