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

Annotations already declare the full safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=false), so the bar is lower. The description adds one genuinely useful piece of context beyond them — that this is reviewer-restricted — but says nothing about reversibility, what state is destroyed, or whether repeated calls overwrite a prior review.

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?

It is a single, front-loaded sentence with no wasted words, but it is terse to the point of under-specification and reads as a noun-phrase fragment rather than a full instruction. Size is appropriate; content density is too low for the tool's complexity.

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?

This is a destructive, reviewer-gated mutation with 8 parameters (6 required), 0% schema description coverage, nested objects, and an output schema. For that complexity the description is drastically incomplete — no auth/permission detail, no side-effect or overwrite semantics, and no guidance on the nested remedyBurden object.

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 0%, so the description must carry the parameter burden. It merely enumerates five of the eight field names (conventionVersion, scanVerified, sensitiveClaimClass, remedyBurden, decision) with no format, allowed values, or meaning — e.g. it never explains what 'sensitive class' or 'remedy burden' should contain, and omits ruleId, reviewerId, and notes entirely.

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+resource ('mutation recording' of a rule review) and a scope constraint ('Reviewer-only'), which sets it apart from the analyze_* siblings. However it is a sentence fragment and never names related siblings such as list_rule_review_queue, validate_rule_spec, or search_reviewed_rules, so differentiation is only partial.

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 only usage signal is 'Reviewer-only', which hints at eligibility but does not say when to use this tool versus validate_rule_spec or list_rule_review_queue, nor any when-not conditions or prerequisites. Effectively no routing guidance.

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