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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful scope (only unpublished posts are touched), but leaves open what happens when post_id refers to an already-published post — a silent no-op, an error, or a skip — and whether the removal is recoverable.

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?

One sentence, effect front-loaded, with the scoping caveat appended. No redundant restatement of the title and no padding.

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 single-parameter destructive tool whose annotations already state destructiveness and idempotency, this is nearly sufficient. The only meaningful omission is the behavior on an already-published or invalid post_id.

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 100% and the schema itself explains that post_id comes from schedule_post or list_scheduled_posts. The description adds no further meaning about the parameter, which is acceptable given the schema already does the work, but nothing is gained either.

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 (removes) and resource (a scheduled post from the Content Plan) plus the intended effect (will not be published). The 'not gone out yet' qualifier scopes it away from post-publishing tools, though it never names reschedule_post as the sibling to use instead.

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?

'Posts already published are not affected' gives an explicit boundary condition for when this tool does not apply. However, there is no guidance on the natural alternative (reschedule_post) when the user actually wants to change the time rather than cancel, leaving that routing to inference.

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