list_drafts

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

No annotations are supplied, so the description carries the full behavioral burden. It adds only that Bcc recipients are included; it does not disclose ordering, pagination/truncation behavior, permissions, or whether drafts are summarized versus fully returned.

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 definition is a single front-loaded sentence with no filler. However, it spends its only clause on Bcc inclusion while leaving more important operational detail unaddressed; still, the sentence itself is appropriately sized.

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 simple list tool with one optional parameter and an output schema, the description is still incomplete: no annotations, no parameter semantics, and no indication of scope, ordering, or limits. It states the resource but not enough to call it confidently beyond defaults.

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 sole parameter max_results has 0% schema description coverage and the description does not mention it. The name and default hint at result limiting, but there is no added meaning about allowed range, pagination, or default behavior.

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 states a clear verb-resource pair ('List drafts in the mailbox') and adds a content detail about Bcc recipients. It is distinguishable from create_draft/update_draft by its list/read action, though it does not explicitly name a sibling alternative.

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?

There is no when-to-use, when-not-to-use, or alternative guidance. An agent can infer that this lists drafts, but it gets no direction on choosing list_drafts over search_threads/get_message or on preconditions.

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