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

With no annotations, the description carries the full behavioral burden. It does disclose the primary effect — moving a scheduled variant back to draft — which is meaningful. However, it does not clarify whether the action is reversible, whether it removes the post from any scheduling queue, or what happens to related data.

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 the action and target, making it an excellent model of conciseness.

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 simple one-parameter mutation, the description covers the core behavior, but it omits helpful context like how to identify the variant (e.g., via list_scheduled_posts) or edge cases (e.g., already published variants). The sibling tool list suggests some context, but the description itself is somewhat bare.

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 coverage is 0%, so the description must compensate. The term 'scheduled variant' provides some semantic connection to the required variant_id parameter, implying the ID identifies the scheduled variant. But it does not specify how to obtain the ID or any format expectations, leaving room for ambiguity.

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 ('Pull') with a clear resource ('a scheduled variant') and outcome ('back to draft'). This makes the tool's core function clear and distinguishes it from siblings like schedule_post or publish_now, though it does not explicitly name those alternatives.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies the use case (undoing a scheduled post), but does not state what preconditions apply (e.g., variant must still be scheduled, not already published) or mention related tools like list_scheduled_posts.

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