list_drafts

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

No annotations are provided, so the description carries the full burden. It discloses that the tool lists subjects and recipients, but does not specify the complete return structure (e.g., draft ID, snippet, timestamp) or whether it only returns metadata. It is a read-only operation, but this is not explicitly stated.

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 concise, consisting of one short sentence that front-loads the multi-account capability. Every word earns its place, though it could be slightly more structured (e.g., separating the multi-account note from the listing function).

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 few parameters and no output schema, the description is adequate. It explains the core function and scope. However, it lacks details on the output format, pagination, or how drafts are ordered, which would help the AI agent fully understand the tool's behavior.

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 coverage is 100% (both parameters described in schema). The description adds context about multi-account support but does not add meaning beyond the schema for the parameters themselves. Baseline 3 is appropriate.

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 that the tool lists saved drafts, specifies it works across multiple Gmail accounts, and mentions the fields returned (subjects and recipients). This distinguishes it from sibling tools like create_draft, delete_draft, and send_draft.

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 provides context that it supports multiple accounts, but does not explicitly state when to use this tool versus alternatives (e.g., search_threads for finding drafts by criteria). No exclusion criteria or when-not-to-use guidance is given.

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