Cancel a scheduled publish

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

Adds rich context beyond annotations: explains status change to draft, clears scheduled_publish_at, content untouched, no-op behavior, and auth requirements. No contradiction with annotations, which only indicate false read-only and destructive hints.

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 sentences, each adding essential information: action, state changes, no-op behavior, and auth. No filler or redundancy; front-loaded with the primary purpose.

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 tool with one parameter and no output schema, the description covers all critical aspects: behavior, side effects, prerequisites, and edge cases. Sufficient for an agent to correctly invoke the tool.

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 has full coverage (id is 'A UUID'), but description adds clarity that the id refers to an article and is used to target the scheduled publish. This goes beyond the schema's minimal description, providing useful semantic context.

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 tool cancels a scheduled publish, with specific actions on article status and scheduled timestamp. It distinguishes from siblings by noting publishing is a separate call, differentiating from publish_article and schedule_article.

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?

Provides clear context of when to use (on scheduled articles) and no-op for non-scheduled. Mentions publishing is a separate call, implying alternatives, but does not explicitly name sibling tools or list when-not-to-use scenarios beyond the no-op case.

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