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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds substantive consequences: it cancels any existing schedule, marks the post queued, and hands it to the publish worker. It also discloses the refusal states, which is exactly the kind of precondition an agent needs before invoking a destructive mutation, and the idempotency semantics in the schema reinforce retry safety.

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?

Three tight sentences: the action is front-loaded, the side effects follow, and the workflow hint closes. No filler, and the most decision-relevant fact (immediate publish, schedule cancelled) comes first.

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 destructive mutation with no output schema, the description covers side effects, state transitions, and failure preconditions well. The remaining gap is that it does not say what a successful call returns (e.g., post ID and queued status), which an agent would need to chain follow-up calls in this multi-tool publishing workflow.

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%, so all three parameters and their purposes are already fully documented, including the 10-minute idempotency window. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource with an explicit scope qualifier: 'Publishes a draft or scheduled video post immediately (no delay).' An agent can distinguish this from scheduling tools via the 'immediately/no delay' framing, but the two direct siblings, batch_publish_now and schedule_post, are never named, so it stops short of full sibling differentiation.

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?

Gives a clear when-to-use signal ('immediately, no delay') plus explicit when-not conditions — refuses posts already queued, processing, published, or terminal. The 'Typical flow: create_post_draft → publish_now' anchors it in a workflow. Missing is routing guidance for the obvious alternative, batch_publish_now, when multiple posts must go out.

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