List drafts

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

The annotations already establish the read-only, idempotent, non-destructive nature of the tool, so the safety profile is covered. The description adds the default sort order but does not go beyond that to describe pagination behavior or what exactly is returned.

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 a single, front-loaded sentence with no filler. Every word contributes to understanding what the tool does.

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?

Adequate for a simple read-only listing tool: the annotations cover safety and the schema covers paging and ordering. However, there is no output schema and the description does not describe the returned draft shape, so the agent must infer some behavior.

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 description adds almost no parameter-level meaning beyond the input schema. It paraphrases the default ordering but does not clarify limit, offset, publication, order_by, or order_direction. With schema description coverage at 60%, the description does not compensate for the remaining gaps.

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 uses a specific verb ('List') and a clear resource ('unpublished drafts'), and adds the default ordering behavior. This distinguishes it from siblings like list_posts, search_posts, and get_draft without requiring schema inspection.

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 intended use is implied: call this when you want to enumerate drafts. However, it does not explicitly state when to prefer it over related tools such as search_posts or list_posts, nor does it name any alternatives.

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