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

With no annotations, the description carries the behavioral disclosure burden. It does communicate the paid nature and aggregated scope, but it does not mention the two-step payment flow (omit header to receive requirements, then call again) or what happens on invalid payment. The parameter schema covers that flow, but the description itself adds limited behavioral depth.

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 short and front-loads the key facts: price, one-call aggregation, and scope. The phrase 'priced below the sum of the parts' is slightly promotional and adds little operational value, so it is not perfectly concise.

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 single-parameter paid tool, the description is mostly complete: it names the metrics included, the cost, and the advantage over alternatives. There is no output schema, so some details about the exact response format or error behavior are not specified, but the low parameter complexity keeps this from being a critical gap.

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 baseline is 3. The description adds context about pricing and route-specific payment, but it does not add meaning about the x402Payment parameter beyond what the schema already explains.

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 states exactly what the tool does: it returns a cross-chain risk snapshot combining distress, venue stress, gas, and bad-debt in one call. This clearly distinguishes farm_mesh from its more specialized sibling tools.

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 phrase 'One round trip instead of five' clearly implies the tool should be used when several risk metrics are needed together rather than calling the individual sibling tools. It does not, however, explicitly say when NOT to use it, such as when only a single metric is needed.

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