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

Beyond its annotations, it discloses that removing all platforms reverts the post to DRAFT, that post actions like auto-retweet are deleted, that the action is not reversible, and that it needs the user's explicit confirmation. This is exactly the operational context an agent needs before causing destruction.

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?

Four short sentences, front-loaded with the destructive action, then side-effects, then prerequisites, then edge-case behavior. 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?

The annotations declare a destructive, idempotent, closed-world mutation, the output schema covers return values, and the description supplies the missing pieces: side effects, reverting behavior, and the confirmation requirement.

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?

The schema documents both nested parameters, and the description adds meaning by noting that passing every scheduled platform removes them all at once, and that only SCHEDULED posts can be unscheduled. It does not say whether an empty array is rejected or what the response looks like, but the core semantics are reinforced.

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 definition uses a specific verb+resource pair ('Cancel the schedule ... on a SCHEDULED post') and names the fields affected (platforms). It also tells the agent apart from the read-oriented siblings 'get_schedule' and 'update_schedule' by explicitly stating what happens to the post.

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 definition gives clear preconditions: only SCHEDULED posts can be unscheduled, explicit user confirmation is needed, and it names 'get_schedule' as the tool that shows currently scheduled platforms. It does not explicitly say when to prefer it over 'update_schedule', which is an alternate mutation of the same resource.

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