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

Annotations already flag destructiveHint=true, so the safety profile is covered, but the description adds genuinely new behavioral information: deletion cascades to queued workflow items. It still omits irreversibility and what happens to already-published posts from that workflow, which would matter for a destructive operation.

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?

A single tight sentence with the verb front-loaded and no filler. It is appropriately sized for the information conveyed, though there is little structure beyond the one clause.

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?

An output schema exists, so return values need no explanation, and the cascade behavior is disclosed. However, for a destructive tool whose parameters are entirely undocumented, the definition leaves an agent without enough to call it confidently with an idempotency key or to understand failure/partial-delete behavior.

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 and does not. It never identifies 'id' as the workflow identifier or explains the role of 'idempotency_key' (e.g., safe retries), leaving both parameters undocumented in any form.

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 ('Deletes') and resource ('a workflow'), and the phrase 'queued workflow items linked to it' clarifies the cascade scope. It is clearly separable from get_workflow/update_workflow/create_workflow, though it never explicitly contrasts with cancel_post, which is the nearest sibling for stopping queued work.

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?

No when-to-use or when-not-to-use guidance is given. An agent deciding between delete_workflow and cancel_post (which presumably stops queued items without removing the workflow) gets no routing signal, and no prerequisites or confirmation requirements are stated.

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