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

Annotations already supply destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds genuinely new context: the deletion is permanent but the call log survives, scoping exactly what is destroyed. It stops short of covering auth requirements or recovery options, so not a 5.

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 with no filler, and the permanence warning is front-loaded ahead of the softer context. Every sentence carries information the agent needs.

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 no output schema and full annotation coverage, the description covers what is deleted, what persists, and the precondition check. It omits error behavior for an invalid or already-deleted id, which keeps it just under complete.

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% for the single `id` parameter, so the baseline is 3. The description only reinforces that the identifier should be verified, without disambiguating whether `id` is a recording id versus a call id — a real ambiguity given siblings like list_calls and get_waveform.

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 remove a call recording") and clarifies the blast radius by noting the call log remains — that distinction matters against the many other delete_* siblings. It doesn't name an alternative tool, but no sibling overlaps this resource, so a 4 is warranted.

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?

"Confirm the identifier before deleting" is a caution rather than a when-to-use rule, and no alternative or when-not condition is given. Usage is implied by the tool name (use this to remove a recording you no longer want), which lands it at minimum-viable rather than explicit guidance.

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