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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is known; the description still adds real context by naming exactly what is destroyed (the task and its cached findings), the ownership constraint, and that repeat calls surface not_found. That last point usefully nuances what "idempotent" means here, though it sits close enough to the annotation that it could read as a partial tension rather than a contradiction.

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 tight sentences with no filler: the destruction is front-loaded, the availability note follows, and the non-effects and repeat-call behaviour close it out. Every clause carries information an agent would otherwise have to guess.

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 single-parameter destructive tool with an output schema, the description covers scope, side effects, exclusions, and repeat behaviour. The only omission is error/permission handling beyond not_found, which is a minor residual gap rather than a blocker to correct invocation.

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% with a single well-documented task_id, so the schema carries parameter meaning. The description adds only indirect semantics via the ownership and organisation scoping, which implies the identifier must belong to the caller's tenant but does not spell out behaviour for an out-of-scope or malformed id.

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 and resource ("Permanently deletes an automated task") plus ownership and tenant scope ("owned by the current user in the connected organisation") and the payload affected ("cached findings"). This cleanly separates it from read-side siblings such as get_task_status and list_tasks, and from the unrelated delete_asset and delete_strategy.

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 a clear applicability condition ("Available in any execution state") and strong exclusions: it does not cancel a running analysis, delete the innovation, or withdraw a professional service request. The gap is that it never names which sibling to use for those alternative intents, leaving the agent to infer the routing.

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