List drafts

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds genuinely new behavioral context — result ordering (newest first) and the fields each entry carries — but says nothing about result size, pagination, or what happens when no drafts exist.

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?

A single tight sentence with zero filler, front-loaded with the verb and resource followed by the two most decision-relevant result facts (ordering and included fields). Every clause earns its place.

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 no-parameter, read-only enumeration tool with no output schema, the description supplies the essentials: what is returned and in what order. The only omission is pagination/size behavior, which is a minor gap given the bounded, non-open-world scope implied by openWorldHint=false.

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?

The tool takes zero parameters, so the schema has no semantics to add and the baseline is 4. The description correctly avoids inventing parameters and instead uses the space to describe the result shape.

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 (List) and resource (saved drafts) and adds two useful output attributes: ordering ('newest first') and returned fields ('status', 'whether they were published'). It distinguishes itself implicitly from get_draft (singular) and the create/edit/delete/export_draft siblings by being the enumeration tool, though it never names those siblings explicitly.

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?

Usage is implied by 'List saved drafts' — an agent can infer this is for enumerating all drafts rather than fetching one. However, there is no explicit guidance about when to prefer this over get_draft, nor any exclusion or prerequisite (e.g. whether drafts must exist).

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