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

Goes well beyond the readOnly/non-destructive annotations: it discloses cost and auth (free, no key), data freshness (as of the last daily read, with measured_at), and two edge cases — an unregistered id returns a plain "is not registered" message, and an uncensused agent returns in_census: false. Those are exactly the failure modes an agent needs to interpret a result.

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?

Front-loads the purpose, then routing, then returns, then freshness and edge cases — a sensible order with no filler. The return-value enumeration is long, though it is doing necessary work because there is no output schema.

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 carries the return contract itself and does so thoroughly: uptime, response time, escrow jobs, delivery rate with its exclusion rule, price-naming, third-party ERC-8004 ratings, and a decomposed 0-100 evidence score. Nothing needed to call it or read the answer is missing.

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 the format detail (digits only, not an address, not another chain's id) is already documented. The description still adds provenance — where a valid candidate id comes from — which the schema does not say.

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?

States a specific verb and resource: "Get the measured track record of ONE AI agent on BNB Smart Chain by its ERC-8004 id." The capitalised ONE plus the id-based lookup make it clearly distinct from the census and evidence-listing siblings.

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?

Explicitly says to use this when a candidate id is already in hand (from find_agents_on_bnb_chain or bnb_agents_by_evidence) and directs the agent to those two tools to find candidates first. Both the when and the alternative are named, not implied.

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