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

Despite readOnlyHint and openWorldHint annotations, the description adds meaningful behavioral context: the $0.01 USDC fee via x402, the types of submitted payloads, the color-coded verdicts, and the specific risk factors checked. This goes well beyond the annotations without contradicting them.

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 dense but well-structured: cost and timing are front-loaded, the input and output are stated concretely, and the safe-action policy is explicit. The closing 'Same as POST /v1/check' is a useful pointer without adding bloat.

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?

Given no output schema, the description still explains what the agent will receive: green/orange/red with reason codes covering spender flags, sanctions, allowances, and token risks. It also covers cost, when to call, and how to act on results, making it complete for an agent to use correctly.

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%, so the baseline is 3. The description reinforces which payload types map to which parameters and gives examples like Permit2 and Seaport, but most parameter meaning already lives in the schema. It adds moderate context but does not carry the semantic burden.

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 identifies a specific action: a pre-sign risk check that evaluates transactions, approvals, and signatures and returns green/orange/red with reason codes. It does not explicitly differentiate itself from siblings like presign_quick_check, but the resource and behavior are unmistakable.

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 gives strong when-to-use guidance: call before signing, proceed only on green, ask the user on orange, and never sign on red. It does not explicitly contrast with sibling tools or state when to choose a quick check instead, so it stops short of a 5.

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