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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description's only added behavioral value is the required scope, which is a genuine but thin addition; it says nothing about irreversibility, cascade effects on related compliance items, or failure modes.

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, zero padding, with the core action front-loaded and the scope requirement second. Nothing is wasted.

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 delete tool whose annotations already declare destructive and idempotent semantics and whose schema fully documents the id, the description covers the essentials. The remaining gap is the absence of any note on irreversibility or related-record impact, but there is no output schema to explain and no nested parameters to document.

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?

There is a single required id parameter with 100% schema description coverage including a UUID format and pattern, so the schema carries the full burden. The description's phrase 'by ID' adds no format or lookup detail beyond the schema, making the baseline of 3 appropriate.

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 (compliance record) with an identifying key (by ID), so an agent immediately knows the operation. It does not, however, distinguish itself from the nearest sibling update_compliance_record beyond the verb, and no scope/behavioral contrast is drawn.

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 description supplies a precondition (compliance_records:write scope) which tells the agent whether it can call the tool, but gives no guidance on when to delete versus update or archive, nor any warning about irreversibility.

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