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

With no annotations, the description is the only source of behavioral information. It discloses the key state transition: a scheduled variant becomes a draft. However, it does not mention permissions, reversibility, or whether the original scheduled item is fully removed or simply reverted, leaving some ambiguity for a mutation-like operation.

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, short, front-loaded sentence with no filler. Every word contributes meaning, and the core behavior is immediately clear.

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?

The tool is simple, with one required parameter and no output schema, and the description conveys the essential state change. However, it leaves the agent to infer the precise identity and source of variant_id, and it offers no guidance about related sibling tools, so the description is adequate but not complete.

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 0%, so the description must compensate for the undocumented variant_id parameter. It offers only a hint that the variant is 'scheduled', but it never explicitly explains what variant_id refers to, where to find it, or what format it should take.

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 states a clear action ('pull back to draft') and the resource ('a scheduled variant'), so an agent can tell this tool un-schedules a post. It does not explicitly differentiate from siblings like publish_now or schedule_post, but the meaning is reasonably unambiguous.

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 the tool is used when a scheduled post should no longer be scheduled, but it provides no explicit guidance on when to choose it over alternatives such as publish_now, schedule_post, or listing scheduled posts. There is no exclusion criteria or mention of prerequisites.

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