mail_deleteCatchAllV1

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

The description explains the behavioral outcome (messages no longer routed) but lacks details on prerequisites, error states, idempotency, or required permissions. Since no annotations exist, the description carries the full burden but falls short.

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 concise sentences: first states the action, second explains the consequence. No wasted words. Front-loaded with the verb-delete.

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 simplicity (1 param, no output schema), the description is mostly complete. It explains the effect but could mention that the catch-all must exist. Missing error handling or return value info.

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?

The input schema covers 100% of parameters, so baseline is 3. The description does not add any additional meaning beyond the schema's 'Catch-all resource ID'. No extra context provided.

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 a catch-all') and the effect ('Messages sent to unknown addresses... are no longer routed'). It distinguishes from siblings (create, list, resend) by focusing on deletion.

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?

The description implies when to use (when you want to stop routing unknown addresses) but does not explicitly state when not to use or mention alternatives. No comparison with sibling tools.

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