gmail_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 disclosure burden, yet it only states result ordering. It says nothing about pagination behavior (despite a page_token parameter), auth/account requirements, or rate limits, leaving an agent to discover these at call time.

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?

One short sentence with the core action front-loaded and zero filler; it is efficiently structured, though arguably terse to the point of under-specification.

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?

With no annotations, no output schema, 33% parameter coverage, and a paginated list operation whose pagination is never explained, the definition leaves significant gaps an agent would need to resolve before calling it correctly.

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 33% — only 'email' is documented, while 'page_token' and 'max_results' (with its 1-100 bound) are bare in the schema. The description adds no parameter meaning at all, so it fails to 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 gives a clear verb+resource ('List Gmail drafts') and adds ordering semantics ('most recent first'), which distinguishes it from gmail_get_draft (single draft). However, it makes no attempt to distinguish itself from the broader sibling set (gmail_search, gmail_list_labels), so it stops short of full sibling differentiation.

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 guidance, no exclusions, and no mention of alternatives such as gmail_get_draft or gmail_search. Usage is only inferable from the tool name itself, which is exactly the kind of inference a description should eliminate.

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