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

Beyond the readOnly and idempotent annotations, the description discloses a 0.005 USDC cost, determinism, evidence-boundedness, and signed output. These are meaningful behavioral traits that are not present in the annotations or schema.

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 content is dense and front-loaded: the core action, scope, cost, and key behavioral properties all appear in a short span. The punctuation is awkward ('without purchasing.; 0.005'), but every phrase 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?

The description covers the core behavior, cost, and output properties, while the output schema handles return-value details. It could be more explicit about what inputs are expected and what counts as an eligible provider under a mandate, but it is adequate for a zero-parameter read-only tool.

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?

Context reports zero formal parameters and 100% schema description coverage, so the baseline of 4 applies. The description does not document the open-schema input keys, but with no defined parameters this is not a significant 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 uses a specific verb ('Recommend') and a specific resource ('verified eligible provider under a mandate'), and explicitly states the tool does not purchase. This clearly separates it from payment, bridge, and mandate-execution siblings even without naming them.

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 description implies usage context: when a mandate exists and a provider recommendation is needed without purchasing. However, it does not explicitly name alternatives or state when not to use this tool, leaving selection among siblings to inference.

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