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

With no annotations, the description carries the full behavioral transparency burden. It faithfully discloses the mandatory payment, the exact USDC cost, the unusual response-to-supply behavior when unpaid, and the expected first response so the agent won't treat failure as an error.

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?

It's compact and front-loaded with the most important detail (PAID and cost), then moves to response and payment workflow. No filler; every sentence 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?

For a tool with no output schema and no annotations, the description tells what the response includes, what happens when payment, and how the agent should request the score. It does not spell out error states, but the payment gate is sufficient for a minimal 2-param call.

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 parameter definitions are already complete. The description adds value by explaining that x_payment is an encoded x402 authorization needed to get the score, and gives example entity values beyond the schema.

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 ('Get') and resource ('SYRI risk score for a venue'), and names the outputs: risk band and 0-100 composite. This clearly distinguishes it from the sibling status and listing tools without needing to know their schemas.

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?

Gives explicit operational guidance: the free call returns payment terms, paying via x402 with x_payment returns the score. It does not explicitly contrast against the status or listing tool, but the payment flow itself strongly signals when to use this tool.

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