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

Beyond the read-only annotations, it discloses the response size (~1 MB), exact contents, and the always-paid cost model via x402 or a pass covering 25 calls. This is the key behavioral context an agent needs before invoking a paid bulk export.

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 front-loaded with the resource, contents, and size, then follows with use cases and payment terms. It is dense and mostly earns its space, though the payment parenthetical is slightly convoluted.

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?

With no output schema, the description compensates by naming the returned artifacts: every agent's scorecard and the full Bouncer's log in one response. It also covers cost and size, leaving little ambiguity for a zero-parameter bulk export.

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?

The tool takes zero parameters, so semantic burden is minimal; the schema already covers the empty input completely. The description adds relevant context about what the response contains, though no parameter guidance is needed.

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 a specific resource and scope: bulk reputation data for ERC-8004 agents on Base, including every scorecard plus the full Bouncer's log in one response. It distinguishes the tool from single-agent lookups by contrasting it with checking many agents for less than 26 single calls.

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?

It gives concrete use cases: building an index, backtesting a hiring rule, or checking many agents cheaply. The alternative is implied by the 'single calls' comparison, but it does not explicitly name sibling tools such as check_agent or bouncer_log.

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