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

With no annotations available, the description carries the burden of behavioral disclosure. It clearly states the state transition (scheduled → draft), the consequence (won't publish), and idempotency behavior for already-draft posts. It omits edge-case behavior like not-found handling, but the core behavior is transparent.

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 front-loaded with the main effect, then gives practical examples and idempotency details without fluff. Every sentence adds value, and the structure leads with the most important information.

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 two optional parameters and no output schema, the description covers the action, result, identifier strategy, and idempotency. It does not specify behavior when both postId and postName are provided, but that is a minor gap for such a straightforward operation.

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 description coverage is 0%, so the description must compensate. It meaningfully explains postName as the caption/opening words and clarifies when to use it as an identifier instead of postId. postId is left self-explanatory from its name, which is acceptable given the fallback guidance.

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 and resource: cancel a scheduled post, with the precise effect of reverting it to draft so it won't publish. This clearly distinguishes the tool from siblings like delete_scheduled_post and update_scheduled_post, which have different outcomes.

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 concrete usage signals: user phrasings like 'cancel that scheduled post' and 'don't publish Tuesday's post', plus a fallback identification strategy using postName when no id is available. It doesn't explicitly say when to prefer delete_scheduled_post or update_scheduled_post, but the intended use-case is well implied.

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