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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the return value ('signed portable policy artifact') and a critical semantic caveat ('ALLOW is policy only, never wallet authority'). This adds genuine context the annotations do not carry. It still omits what a DENY looks like or any rate constraints.

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?

Only two sentences, with the most important instruction ('Call BEFORE...') front-loaded. Every sentence carries signal; the compression is appropriate for a preflight guard.

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 tool with complex nested inputs and no output schema, the description covers intent, timing, and the authority caveat, but leaves the action/policy parameter mechanics and the DENY path undocumented. Adequate minimum but with clear gaps.

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% for two large nested objects (action and policy, each with many required sub-fields). The description explains the overall framing but nothing about the action/policy split, the required sub-fields, or their constraints, so it fails to compensate for the coverage gap.

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 names a specific action and resource scope: it evaluates a narrow Base USDC-to-WETH direct Uniswap V3 swap and returns a signed portable policy artifact. That scope distinguishes it from preflight_allowance and preflight_payment. Minor deduction because terms like 'OCD' and 'policy artifact' are jargon an agent must infer.

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?

It gives explicit timing guidance ('Call BEFORE an agent asks its wallet to execute...'), which is the key decision point for a preflight tool. It does not name the alternative preflight/inspect siblings or state when-not to use it, so it stops short of full routing guidance.

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