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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation and external side effects are partially covered. The description adds genuine value beyond them by disclosing the quota refund side effect and the 'when applicable' condition, though it says nothing about failure modes or reversibility of the cancellation.

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 sentence that front-loads the verb and resource, then attaches the precondition and side effect in a compact clause. No filler, nothing to trim.

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, one-parameter tool with no output schema and no annotations covering the refund, the description covers the essentials (what is cancelled, the precondition, the refund). It omits what happens on failure (e.g., already-published publishId) and any confirmation or irreversibility note, leaving gaps for an agent handling edge cases.

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% for the single required publishId parameter, so the description should compensate but instead only vaguely refers to 'a content post' without explaining where publishId comes from or what it identifies. The parameter's name and UUID format in the schema make it largely self-evident, keeping this at a minimum-viable 3.

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 pairs a specific verb (cancel) with a specific resource (a not-yet-published content post) and adds scope ('not-yet-published'), which separates it from mutation siblings like update_content_publish or publish_content. It stops short of naming the sibling alternatives it should be chosen over, so it is clear but not fully differentiated.

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?

It gives a clear precondition for use: only posts that have not yet been published at the provider are cancellable, which implicitly excludes published posts. It offers no explicit alternatives (e.g., update_content_publish, delete_content_piece) for cases where the post is already live, so guidance is clear but not exhaustive.

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