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

Annotations already declare destructiveHint=true, and the description never warns that the current template is destroyed or that the action may be irreversible. It adds no behavioral context beyond the flag, and does not mention idempotency or auth requirements.

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?

Very short, but the single sentence is not front-loaded and contains no operationally useful detail. Brevity here masks underspecification rather than avoiding waste.

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?

A destructive mutation with no output schema and zero schema descriptions is missing too much: no confirmation of what changes, no permissions, no response shape. The description does almost none of the work the structured fields leave undone.

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% and all three parameters are undocumented. The description weakly explains the email_type values but says nothing about request_id or idempotency_key. It does not compensate for the coverage gap.

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 says 'reset an email' which restates the title but does not specify what is reset (customization, content, layout) or that it restores the built-in default. Sibling tools like delete, rollback, and duplicate make the action ambiguous without opening the schema.

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 indication of when to use reset versus rollback, delete, or recreate. The only guidance is a parameter value rule, not a when-to-use condition. An agent cannot tell which email tool to pick from this description alone.

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