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

The annotations flag destructiveHint=true, but the description adds real substance beyond them: exactly what is destroyed (schedules stop, guest share links die, evals can no longer run, binding shows flowOk: false) and the confirmation round-trip ('May return needs_confirmation'). This is precisely the consequence-level detail an agent needs before a destructive call.

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?

Front-loads the core action and its consequences, then appends the pre-check guidance and the re-confirmation note. Dense but every clause carries distinct, load-bearing information 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 destructive mutation with no output schema, the description covers the blast radius, the pre-flight checks, the softer alternative, and the confirmation protocol. An agent has everything needed to invoke it safely and correctly.

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 100%, so flowId, workspace, and approvalId are all documented in the schema. The description reinforces the approval flow by mentioning the needs_confirmation response, but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('Deletes a flow') that unambiguously states the operation. It is clearly distinguishable from sibling tools like workbench_flows_update or workbench_flows_schedules_delete, which it even references by name.

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 explicit when-to-use guidance ('check caliper_flow_performance for evals and workbench_flows_schedules_list before proposing') and names a concrete alternative with the selecting condition ('prefer workbench_flows_update with archived: true when the user just wants it out of the way'). No routing decision is left to inference.

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