list_drafts

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

No annotations are provided, so the description carries the full behavioral burden. "List" implies a read, but the definition doesn't state whether it is side-effect free, whether results are user-scoped, how "local" differs from server-side drafts, ordering, or whether an empty result is possible. The output schema covers return shape, but the operation's semantics remain under-disclosed.

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 single sentence is front-loaded with the verb and free of padding. However, its extreme brevity reflects under-specification rather than disciplined economy, leaving key scoping ambiguous.

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 zero-parameter list tool with an output schema, the description is minimally viable, but with no annotations the meaning of "local" and the relationship to other draft tools are unresolved. It stops short of what an agent needs to decide between list_drafts and siblings like preview_draft or my_ads.

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 there is no parameter semantics to document. Baseline 4 applies, and the description introduces no confusing parameter claims.

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?

"List local drafts" states a specific verb (list) and resource (drafts), with the modifier "local" narrowing scope. Siblings like create_draft, update_draft, and publish_draft are clearly different operations, though the description never explicitly contrasts itself with them.

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?

There is no guidance on when to call this tool, what precondition makes drafts "local," or which sibling to use instead (e.g., preview_draft or push_draft). The agent must infer usage entirely from the name.

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