list_drafts

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

The description states 'Read-only', which is helpful given no annotations. It also notes a maximum limit of 100. Missing details on authentication, empty results behavior, or whether the list is paginated beyond the limit.

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?

Two sentences with no filler. Front-loaded with the core action and ordering. Every sentence adds necessary information.

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 list tool with simple parameters and an output schema, the description covers filtering, sorting, and safety (read-only). Could mention pagination details but not required.

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 0%, so the description compensates by explaining all three parameters: status (with explicit allowed values), account (by account id), and limit (max 100). Default values are in schema but not repeated; still adds value.

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 verb 'List' and the resource 'drafts', specifies the ordering 'newest first', and distinguishes from sibling tools like get_draft (single draft) or reject_draft (mutation).

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 implies usage context: listing drafts with optional filters. The 'Read-only' label guides safe usage. It does not explicitly contrast with alternatives like get_draft, but the purpose is clear.

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