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

Annotations already flag destructiveHint=true, and the description adds exactly the consequences an agent needs beyond that: scheduled posts are removed from the library and the workflow will not pick that source post again. It also discloses the failure mode for already-published reposts, which no annotation conveys.

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?

Three sentences, each with a distinct job: what happens, parameter provenance, and failure condition. Effects are front-loaded before the parameter note, with no filler.

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 2-parameter destructive tool with no output schema, the description covers effect, side effects, parameter sourcing, and failure conditions. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description earns extra by disambiguating post_id as the workflow entry id rather than a platform post id, and by naming the source tool for each parameter. It adds meaning beyond the field descriptions, though not format details.

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?

Specific verb (cancels) + resource (an upcoming repost from a Repurposing workflow) with the scope qualifier 'from a Repurposing workflow' that separates it from the sibling cancel_scheduled_post. An agent can identify the action and its domain without opening the 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?

Explains the preconditions ('fails if the repost has already gone out') and points to both prerequisite lookup tools (list_repurposing_workflow_posts for post_id, list_repurposing_workflows for workflow_id). It does not explicitly contrast with cancel_scheduled_post or delete_repurposing_workflow, so it falls short of naming alternatives.

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