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

With no annotations, the description carries the full burden. It usefully discloses that the tool is paid ($0.05 USDC), a real behavioral trait beyond the schema, and paymentSignature in the schema explains the x402 challenge-then-retry flow. However it says nothing about what the review returns, depth of analysis, or limits on contract size.

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 sentence, front-loaded with the payment constraint before the purpose. Efficient, though the enumerated risk list is somewhat long without adding routing value.

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 4-parameter paid tool with no annotations and no output schema, the description covers cost and scope but omits return-shape expectations and any indication of analysis depth. Adequate but with clear gaps an agent would want filled before calling.

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 100%, so the schema already documents text, title, counterparty and paymentSignature. The description adds no syntax or format detail for these parameters, so baseline 3 applies.

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 (reviews) and resource (vendor contracts) plus an enumerated scope of risk signals (renewal, lock-in, service, data, liability, commercial). This is clear enough to distinguish from extraction siblings, but it never differentiates itself from the close cousins analyze_contract_risk or compare_contract_risk.

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 when-to-use guidance and no mention of alternatives, despite siblings like analyze_contract_risk and compare_contract_risk doing overlapping work. The agent must infer from the name alone whether this is the right risk tool to call.

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