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

Annotations already declare destructiveHint=true, and the description adds real value beyond them: existing evals retain a snapshot and keep running, nothing new can bind to the rubric, and a `needs_confirmation` response may occur (linking to the approvalId param). This is exactly the consequence-level context a destructive tool needs.

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, front-loaded sentences with no waste; the core action leads and the consequences and confirmation behavior follow compactly.

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, no-output-schema tool, the description covers the key behavioral facts (retention, binding block, confirmation flow). Minor omissions remain, such as explicit irreversibility wording, but nothing an agent critically needs is missing.

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%, so all three parameters are already documented (including the approvalId/needs_confirmation linkage). The description adds nothing beyond what the schema provides for parameters, so the baseline 3 applies.

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+resource ('Deletes a rubric'), which is unambiguous against the sibling set (rubrics_create/get/list/update). It does not explicitly differentiate itself from alternative lifecycle operations, but the operation is clear from the phrasing.

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 explains consequences of deleting but gives no guidance on when to delete versus alternatives (e.g., update vs delete), nor any prerequisites for invoking it. Usage is only implied by the verb.

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