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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered elsewhere. The description adds nothing beyond a pricing note — no mention of pagination behavior, filtering scope, or what the listing returns, even though those behaviors matter for a paginated list endpoint.

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 just a duplicated title plus an HTML-commented pricing block, which is noise for an agent and not front-loaded useful information. It is short but wastes what little space it has.

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 six-parameter paginated list tool surrounded by many similar draft/sibling getters, the description should at least state scope (all drafts vs. inbox-scoped drafts) and that results are paginated. The output schema exists, but the description fails to disambiguate from siblings, leaving the agent under-informed for this complexity.

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 100%, so all six parameters (after, before, limit, labels, ascending, page_token) are already documented in the schema. The description adds no parameter meaning beyond that, which meets the baseline of 3.

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 is simply 'List Drafts', which restates the title verbatim and provides no distinguishing detail from the closely related siblings get_agentmail_inbox_drafts, get_agentmail_draft, and get_agentmail_inbox_draft. The only added content is a pricing banner, which does not clarify the tool's purpose.

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 guidance on when to use this tool versus get_agentmail_inbox_drafts or the singular draft getters. An agent has no basis for choosing among the many list/get draft siblings.

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