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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known. The description earns credit for clarifying the blast radius — cancellation does not remove content already published to the platform — and for promising a publishing receipt. It does not discuss failure modes, such as cancelling a post that is mid-publish.

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, both load-bearing: the first gives action, identifier, and result; the second gives the negative scope. Nothing is padded and the key fact is front-loaded.

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?

With an output schema present, return values need not be described, and annotations cover destructiveness and idempotency, so the definition covers the essentials for a one-parameter cancel tool. The only gap is guidance on edge cases like a post already in flight.

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?

There is a single parameter with 100% schema description coverage, and the schema already says it comes from list_posts. The description only restates 'identified by post_id' and adds no format, sourcing, or validation detail beyond the schema, so the baseline of 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 ('Cancel') and resource ('a scheduled post') plus the identifier used to target it, which is precise enough that an agent can distinguish it from a delete operation. It does not explicitly name or contrast a sibling such as delete_post or cancel_job, which keeps it short of a 5.

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?

Usage is implied by the phrase 'a scheduled post' — an agent can infer it applies only to not-yet-published items, and 'Does not delete already-published platform content' sets a boundary. However, no alternative tool is named and there is no explicit statement of when to prefer this over a deletion or update path.

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