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

Annotations already declare destructive and idempotent, so safety is structured; the description adds what the annotations cannot — the set of eligible states (scheduled, awaiting approval, missed). It does not state whether cancellation is reversible or what happens to the post record afterward, which would be the remaining behavioral gap.

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?

Two short sentences with the eligibility rule front-loaded and the exclusion second. No filler, no restatement of the tool name.

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?

A one-parameter mutation tool with annotations covering safety and no output schema needs little more than eligibility rules, which are present. The only missing piece is guidance on sourcing postId and the outcome of a successful cancel.

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% and the single parameter postId is documented only by type, pattern, and length constraints. The description never clarifies what a postId refers to or how to obtain one (e.g., from antix_list_scheduled_posts), so it adds no semantic value 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?

States a specific verb (cancel) and resource (booked post), and bounds the resource to post states that have not gone out. It implicitly separates itself from publish/approve siblings, though it never names an alternative tool.

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 condition (post must not have gone out) and an explicit when-not (already live posts cannot be removed from here). It stops short of saying what to do instead for a live post, so the agent is left without a routing target.

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