x402 bulk trust scoring (paid)

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

No annotations are provided, so the description carries full burden. It thoroughly discloses paid nature, cache staleness (~15 min), recompute limits, response flags (recompute_limit_hit), automatic tier selection, pricing, and found:false behavior. This is comprehensive behavioral transparency.

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?

Although longer than typical, every sentence adds essential operational detail (purpose, outputs, caching, limits, pricing, alternatives). The structure front-loads the primary purpose and then covers edge cases, making it remarkably information-dense without fluff.

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?

Given the tool has no output schema, the description comprehensively explains the return fields (trust score, grade, recommendation, confidence, timestamps, recomputed flag) and all relevant edge cases (not-found, recompute limits, payment behavior). This makes the tool complete for both selection and invocation.

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 baseline is 3. The description adds meaningful context beyond schema: automatic tier selection, pricing for each tier, and the implication that resources not in the observation set still cost money. It also clarifies the 'resources' parameter semantics with the found:false behavior, adding value beyond the raw 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?

The description uses a specific verb ('Score') and resource ('x402 endpoints') in a clear scope ('up to 500' in a 'SINGLE paid call'). It distinguishes from siblings explicitly by naming x402_trust_score as the alternative for fresh live probes.

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?

Provides explicit usage context: suitable for bulk scoring using cached data, with clear guidance that live probing is handled by x402_trust_score. It also warns about paying even for resources not found and explains the per-request recompute limits, helping agents decide when to call this tool.

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