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

Annotations already declare destructiveHint, idempotentHint, and readOnlyHint=false, so the safety profile is covered; the description adds the outcome ('never publishes') and the repeat-safety note. It omits reversibility, permission requirements, and any error behavior for an invalid or already-published task_id.

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?

Two short sentences, zero redundancy, with the operative scope stated first and the limitation second. Every clause earns its place.

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 mutation with full annotation coverage and no output schema, the description covers scope, consequence, and repeat safety adequately. The remaining hole is the identity and format of task_id, which neither schema nor description resolves.

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%, and the description never mentions the single required parameter, task_id. The name is ambiguous next to sibling tools that operate on post ids, so the agent is left guessing whether it must pass a scheduling task id or a post id.

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 (cancels) plus the exact resources it applies to (a post still SCHEDULED, or a DRAFT) and what it does not touch (already-published posts). An agent can distinguish it from publish_draft, update_post, and remove_plan_post without opening any schema.

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?

Implies when to use it (post is scheduled or draft) and gives an explicit when-not (already published). It does not name an alternative tool for the published or plan-post cases, so the agent must infer routing from sibling names.

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