Cancel a scheduled post

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

No annotations are provided, so the description carries full burden. It discloses that the action is destructive ('delete') and prevents publication, but lacks details on reversibility, confirmation requirements, or side effects. For a delete operation, more transparency is expected.

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 sentence that is front-loaded and contains no fluff. It effectively conveys the purpose, though it could arguably be split into separate points for clarity.

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 single-parameter tool with no output schema, the description is largely complete. It covers what the tool does and the required input. Missing elements like error handling or result description are minor given the 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?

The input schema already describes 'job_id' with 100% coverage. The description repeats this ('by job_id') without adding extra meaning, such as format, source, or constraints. Baseline 3 is appropriate.

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 clearly states the verb 'Cancel (delete)', the resource 'scheduled post', and the effect 'so it will not be published'. It uses the parameter 'job_id' to specify which post, and distinguishes from sibling tools like 'edit_scheduled_post' and 'list_scheduled_posts'.

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 implicitly states when to use (to cancel a scheduled post) but provides no explicit guidance on when not to use or alternatives. For example, it does not mention that editing might be preferred over canceling, or any prerequisites.

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