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

Annotations already declare destructiveHint=true, so the bar is lower, but the description still adds real value: published reposts persist, unshipped posts default to drafts, and only 'remove' deletes them. The one gap is that it never states the workflow deletion itself is permanent/irreversible or whether confirmation or special permissions are needed.

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 tight sentences, front-loaded with the action, then consequences, then the parameter caveat, then the alternative. Every sentence carries distinct information and nothing is padded.

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 two-parameter destructive tool with no output schema, this covers survival semantics, default branch behavior, and the non-destructive alternative. It stops short of stating permanence of the workflow deletion itself, the main remaining unknown an agent would want before calling it.

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% and the stop_action parameter already documents both enum values and the 'drafts' default, so the description's rephrasing of stop_action is largely redundant. It contextualizes it slightly ("for a scheduled ('existing') workflow") but adds no syntax or scope detail beyond the schema, which is the baseline-3 case.

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-plus-resource ("Deletes a Repurposing workflow") in the first sentence, immediately followed by what survives the deletion. It also distinguishes itself from update_repurposing_workflow, so an agent can tell the two apart without opening either 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?

Explicitly names the alternative path and its condition: "To stop it for now instead, use update_repurposing_workflow with enabled: false." That is a rare, unambiguous when-not-to-use statement with the substitute call spelled out.

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