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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, so the agent knows this is a mutating, non-idempotent write. The description adds useful context ('auditable') and the boundary on what the tool cannot do, but says nothing about what gets destroyed, permission requirements, or the effect of the idempotency key.

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, front-loaded sentences with no filler; the capability statement precedes the constraint. It is efficient, though arguably too terse given the six undocumented parameters it must carry.

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 6-parameter, 3-required destructive tool with a free-form nested payload, no output schema, and 0% schema coverage, the description leaves payload shape, idempotency behavior, audit requirements, and the response all unexplained.

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 all six parameters rely on the description, yet it only loosely gestures at command_type values and never explains payload (an open nested object), rationale, trace_id, or idempotency_key. Given a destructive non-idempotent tool, the idempotency_key semantics in particular go unaddressed.

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 ('Submit an auditable intake-review command') and enumerates the accepted command intent (review/correct facts, update evidence, escalate). It distinguishes itself from mutation siblings like submit_intake and get_review_command, though it never names a sibling explicitly.

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?

Gives clear scope guidance ('Allowed commands review or correct facts, update evidence, or escalate') plus an explicit when-not ('cannot complete or reopen a case'). It stops short of routing to a sibling for the excluded complete/reopen operations.

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