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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that drafts originate from AI tools and are in a pending state; it says nothing about result size, ordering, or whether drafts from other sources are excluded.

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 compact sentence with no filler, and the scoping information is front-loaded. It is a noun phrase rather than a verb-led statement, which slightly weakens the opening but does not waste words.

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-required-parameter read tool this is close to adequate, and annotations cover the safety posture. With no output schema, however, the description never indicates what a returned draft record contains or how pending drafts are identified, leaving a real gap for the agent.

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 100%, including a detailed enum mapping for app and a clear explanation of store, so the baseline applies. The phrase 'for this store' loosely reinforces the store parameter but adds no syntax or defaults beyond the schema.

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 names a specific resource (drafts / unpublished changes created via AI tools) scoped to a store, which is more precise than the bare title. It stops short of distinguishing the tool from close siblings such as preview_draft or get_item, so an agent must infer that this is the enumeration counterpart.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The clause 'waiting to be published or discarded' hints at the lifecycle context, but the agent is left to infer that it should call this before request_publish or discard_draft.

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