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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds that deletion is permanent and requires explicit confirmation. This goes beyond the annotation by emphasizing irreversibility and the confirmation gate. Authorization is only hinted at via 'authorized ECU file'.

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?

The description is a single, front-loaded sentence with no filler. Every word contributes to stating the action, permanence, and confirmation requirement.

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 delete with an output schema and destructive annotations, the description covers the core safety message of permanence and confirmation. It remains thin on authorization requirements and does not explain the 'id' parameter, leaving gaps for a destructive operation with no schema parameter descriptions.

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?

With 0% schema description coverage across two required parameters, the description must carry the full burden of explaining parameters. It partially clarifies the 'confirmed' parameter through 'explicit confirmation' but says nothing about what 'id' identifies or its expected format.

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?

The description states a specific verb ('delete'), resource ('ECU file'), and permanence ('Permanently'), making the operation clear. It does not explicitly differentiate from sibling ECU file tools or name alternatives, but the verb distinguishes it from inspect/list/process/retry sufficiently.

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?

The phrase 'after explicit confirmation' implies a required precondition, which aligns with the required 'confirmed' parameter. However, it gives no guidance on when deletion is appropriate versus alternatives, nor what to do if confirmation has not been obtained.

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