katto_cancel_scheduled_post

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

Annotations already flag the operation as destructive and idempotent, and the description goes further: it describes the concrete effect (removed from calendar, never published, equivalent to deleting in the dashboard calendar), the state-machine precondition, and the retry semantics ('a second call returns not found').

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?

The core action and its effect are front-loaded, followed by eligibility rules, the confirmation step, retry behavior, and the return shape. Dense but every clause carries distinct operational information with no filler.

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?

Though no output schema exists, the description supplies the return payload ({ id, status: 'cancelled', previous_status }), the error conditions, and the retry outcome. An agent has everything needed to invoke and interpret this tool correctly.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already defines the id and its origin (publish_clip or list_scheduled_posts). The description adds no further syntax or format detail beyond the parenthetical hint to confirm platform, clip, and time, so baseline 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 (scheduled post) with an explicit scope: it is removed from the calendar and will not be published. This clearly separates it from the similarly named sibling katto_cancel_job, which cancels a processing job rather than a scheduled publish.

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 explicit when/when-not guidance: only pending or failed posts can be cancelled, while posting or posted posts return an error. It also adds a procedural precondition that is easy to get wrong (confirm the exact post with the user before cancelling) and explains that a published post cannot be taken down here.

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