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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the core behavioral traits. The description adds value by explicitly stating 'never sends or creates Gmail drafts,' which clarifies the tool's scope beyond the annotations' binary flags. There is no contradiction with annotations.

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 two sentences, front-loaded with the main action, and every sentence adds value. There is no redundant or irrelevant information, making it highly efficient.

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 the output schema exists, the description does not need to detail return values. The tool has a simple interface (one optional parameter), and the description covers its core purpose and safety. However, the lack of parameter documentation is a minor completeness gap, preventing a perfect score.

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 has one parameter (limit) with zero description coverage. The tool description does not mention or explain this parameter. The agent must rely solely on schema properties (type, default, min, max) to infer its purpose, which is insufficient for optimal use. The description fails to compensate for the low schema coverage.

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 tool returns local drafts and approval packets waiting for human review, using a specific verb ('Return') and resource ('local drafts and approval packets'). It distinguishes from siblings by explicitly stating it never sends or creates Gmail drafts, which differentiates it from tools like mission_prepare_email_draft or mission_send.

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 usage context (retrieving items for human review) and emphasizes safety with 'Read-only; never sends or creates Gmail drafts.' However, it does not explicitly provide when-to-use or when-not-to-use conditions or name alternative tools, despite the sibling list offering many related options.

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