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

No annotations are provided, so the description carries the full burden. It usefully discloses that the operation is paid ($12.90 USDC) and high-volume, which is real behavioral context, but it omits payment failure behavior, whether charges are reversible, and rate or capacity failure modes beyond the cap.

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?

A single front-loaded sentence that packs purpose, price, capacity, and output type without waste. It could be marginally tighter, but every clause earns its place.

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?

With no output schema and no annotations, the description should do more to describe the ranked triage result and the paid-flow consequences, especially since real money is involved. The schema covers the x402 payment challenge mechanics, but the agent still lacks a clear picture of cost-of-failure and result shape.

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 only 50%: the paymentSignature parameter is documented inline in the schema, but the contracts array-level semantics are not. The description adds the 'up to 200' capacity bound and the payment context but does not explain the nested contract object fields or what qualifies as valid input beyond what the schema already states.

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 verb (scan) and resource (contract portfolio) and states the capacity cap and the ranked operational triage output. It is clear what the tool does, though it differentiates from the scan_contract_portfolio_50 sibling only implicitly via the '200' in the name rather than through an explicit comparison.

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?

There is no guidance on when to choose this tool over scan_contract_portfolio_50, triage_contract_batch_10, or the single-contract triage tools. The word 'high-volume' hints at scale but never states the selection condition or any exclusivity, leaving the agent to infer usage from the name alone.

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