cancel_scheduled_post

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

With no annotations, the description carries the full burden. It clearly conveys the destructive nature of the action ('Cancel') and the precondition ('pending'). However, it does not state whether cancellation is reversible, what happens if the reel has already been posted, or any other side effects.

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 description is a single concise sentence with no filler. The core action and input source are front-loaded, and every word contributes to understanding the tool.

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 one-parameter tool with no output schema, the description covers the action, required input, id source, and scheduling state. It could mention what result to expect on success or failure, but that is not essential for correct selection and invocation.

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 only says 'id' is a string with no description. The tool description compensates by explaining that id refers to a scheduled reel and pointing to the tools that produce valid ids, which is valuable for correct invocation.

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 ('Cancel'), a clear resource ('pending scheduled reel'), and identifies exactly where the id comes from ('from schedule_reel or list_scheduled_posts'). This clearly distinguishes it from the sibling scheduling and listing tools.

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?

It gives clear usage context: use it to cancel a pending scheduled reel, and the required id is obtained from schedule_reel or list_scheduled_posts. It does not explicitly list exclusions or alternative tools, but the intended scenario is unambiguous.

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