list_drafts

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the trailing 'Read-only' is redundant. However, the description does add real behavior beyond structured data: results are ordered newest-first and the limit is capped at 100, both of which the schema does not express.

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 densely packed sentence, front-loaded with the verb and resource, then filter semantics in the order a caller encounters them. No filler sentences.

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?

Low-complexity read tool with an output schema (so return shape needn't be explained), all three parameters documented, ordering disclosed, and safety covered by annotations. Only gap is behavior when more than 100 drafts exist (truncation vs. paging), which is not addressed.

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 0% and the status parameter has no enum in the schema, so the description carries the full burden — and it does: it enumerates all seven status values, defines account as an account id, and states limit caps the response at 100. This is exactly the compensation a 0%-coverage schema needs.

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?

States a specific verb + resource ('List drafts') and adds the default sort order ('newest first'), which no structured field carries. It does not explicitly differentiate from sibling readers like get_draft, but the singular/plural contrast makes the scope inferable. Clear, just not sibling-routing.

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 filter parameters imply when this tool is useful (narrowing by status or account), but nothing states when to use list_drafts versus get_draft, list_queue, or the draft-mutating siblings. Adequate but leaves selection to inference.

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