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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. Beyond that, the description adds ordering ('soonest-expiring first'), identifies the fields returned, and clarifies 'Listing sends nothing,' which is useful behavioral context for an approval queue.

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 front-loaded sentence communicates the purpose, ordering, returned fields, and side-effect status without waste. The phrasing around 'Replies the automation drafted' is slightly compressed but still understandable.

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 read-only list with one optional parameter and no output schema, the description supplies the essential context: what is listed, ordering, returned fields, and confirmation that listing does not send. It does not enumerate sibling alternatives, but nothing critical for invoking the tool is missing.

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%, and the single limit parameter is fully documented in the schema. The description does not add meaning about the limit or its default range, so baseline 3 applies.

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 resource—reply drafts awaiting the person's approval—and the listing verb. It does not explicitly distinguish itself from siblings like approve_reply_draft or reject_reply_draft, so it falls short of a full 5, but the pending-draft scope is clear.

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?

Use is implied: the agent should call this to see drafts held for approval. There is no explicit when-to-use or when-not guidance, and no routing to approve_reply_draft, reject_reply_draft, or other alternatives.

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