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

With no annotations, the description carries the full burden and does well: it discloses pricing ($0.02 USDC on Base via x402), that no account or API key is needed, the two-call payment handshake, and the 1000-domain cap. It does not clarify whether $0.02 is flat per call or per domain, nor what happens on payment failure or over-limit batches, which matters for a paid tool.

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?

Dense and largely waste-free, with the operation and return shape packed into a few sentences. The pricing block is inserted second, ahead of what the tool actually does, which slightly buries the core purpose, but nothing is redundant.

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 usefully enumerates the return fields (score, grade, 90-day uptime, probe count, distinct on-chain payers) and explains the payment prerequisite. It is close to complete, missing only sibling differentiation and edge-case behavior for large or failed batches.

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 both `days` and `payment` are already documented in the schema, including the omit-vs-supply payment behavior. The description reinforces the payment mechanic but adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 moves past the name-restating opener ('Bulk scoring') to state a concrete operation: post up to 1000 domains and get one scored row back per input row, with named output fields. It is clear what the tool does, but it never explicitly distinguishes itself from the sibling bulk_export, leaving the agent to infer the boundary.

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 explicit operational guidance for the two-step flow: 'Call without `payment` to receive the exact payment requirements, then call again with `payment` to be served.' That is a clear usage sequence. It stops short of naming when to prefer this over bulk_export or other scoring siblings.

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