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

Annotations already declare destructiveHint and idempotentHint, and the description adds useful behavioral nuance: the post and its media are preserved even though the scheduled action is canceled. It does not disclose permission requirements or status transitions, but the annotations lower the burden and there is no contradiction.

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 with no filler: the action is front-loaded, the resource is specific, and the deletion caveat is an essential qualifier rather than extra verbosity.

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 simple two-parameter operation with no output schema and no nested objects, the description plus annotations and schema provide enough to invoke the tool correctly. It could mention state prerequisites or what happens after cancellation, but that is a minor gap given the tool's simplicity.

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%, so the baseline is 3. The description adds little parameter-specific detail, but the schema already clearly documents post_id and request_id, including the client correlation id purpose.

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 uses a specific verb ('cancels') and resource ('a scheduled post'), and adds a clarifying negative scope ('without deleting it or its media'). This makes the tool's purpose immediately clear and distinguishes it from schedule/reschedule and deletion-related operations.

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?

The description provides no guidance on when to prefer this tool over related siblings such as invoke_reschedule_post, invoke_schedule_post, or invoke_publish_now. It implies use for scheduled posts but does not state conditions, prerequisites, or alternatives.

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