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

The description goes beyond annotations by specifying side effects: a signed receipt and 30-day status record, and the caveat that triage does not imply human approval. It also discloses conditional ReviewQueue involvement, which is helpful. However, it does not clarify whether the command itself is executed or only preflighted.

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?

The description is a single, dense sentence that front-loads the purpose and packs in pricing, workflow components, and a caveat. Every phrase adds value; no wasted words.

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?

While the description gives a high-level workflow overview, it leaves out critical specifics: whether the action is executed after a safe decision, and what 'honest decision' entails. The existence of an output schema covers return values, but the description should clarify the preflight nature and relationship to simpler gate tools.

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 100% with detailed parameter descriptions, so the baseline is 3. Tool description adds no parameter-specific meaning beyond mentioning the payment/quota context. It does not explain how parameters like actorType or paymentSignature affect workflow behavior.

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 clearly outlines a complete workflow with DestructGuard evidence, conditional ReviewQueue triage, an honest decision, signed receipt, and 30-day status record. It distinguishes itself from siblings like action_safety_quick_gate by the 'complete' scope, though it lacks an explicit verb like 'runs'.

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?

No explicit guidance is given about when to use this tool versus alternatives such as action_safety_quick_gate or submit_reviewqueue_request. The description mentions conditional triage but does not state when the quick gate should be used instead. This leaves the agent to infer usage from the 'complete' label.

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