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

Goes well beyond the annotations: destructiveHint=true only says it's destructive, whereas the description discloses the soft-delete semantics, the 30-day restore window, and crucially that running executions are not cancelled. It does not mention permission requirements or what happens on a second delete of an already-deleted flow (relevant given idempotentHint=false).

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 short sentences, zero filler, and the most consequential fact (it is a soft delete, not a permanent one) is front-loaded before the recovery path and the caveat about executions.

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 destructive tool with no output schema, the description covers reversibility, retention, and side effects on in-flight runs. Minor gaps remain around authorization requirements and repeated-delete behavior, but nothing essential to calling 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 description coverage is 100% and the single 'id' parameter is already documented as the UUID of the flow to delete, so the description adds nothing parameter-specific. Baseline 3 applies when the schema carries the full burden.

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 plus qualifier and resource: 'Soft-delete a flow.' The qualifier 'soft' immediately separates it from the hard-delete/cancel siblings such as neuron_delete_flow_run and neuron_cancel_flow_run, so an agent can route correctly without inspecting schemas.

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?

It names the recovery counterpart neuron_restore_deleted_flow and the condition under which you'd need it (restore within 30 days). It doesn't explicitly say when to prefer this over pausing/toggling a flow or deleting a run, so it falls short of full when/when-not coverage.

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