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

Annotations only say destructiveHint=true; the description adds genuinely new behavior — the call previews by default and only executes with confirm: true. It does not mention irreversibility, whether report data can be recovered, or side effects on the client record, which keeps it below 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?

Two short sentences, front-loaded with the operation and immediately followed by the gating rule; nothing is padded. It is tersely efficient, though the parenthetical could be a full sentence for readability.

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 tool with an annotation covering the safety hint and no output schema, the description explains the confirmation flow but leaves the post-delete outcome, permission requirements, and reportId provenance unaddressed. Adequate but with clear gaps.

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 50%: the confirm parameter is already fully documented in the schema and the description merely restates it. The undocumented half — reportId — gets no clarification of format, source, or where to obtain a valid 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 (delete) and resource (a client's health report), which cleanly separates it from the only related siblings, list_client_health_reports and upload_client_health_report. An agent can identify the operation without opening the schema.

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 confirm-gating note implies the intended two-step flow, but it never states prerequisites (permissions/ownership of the report), nor when to prefer any alternative such as archiving or listing the report first. Usage is implied rather than spelled out.

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