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

Goes well beyond the readOnly/destructive annotations: it discloses cost and auth ("Read-only, free, no key"), data freshness ("from the last daily census"), and the failure mode ("No match returns returned: 0, not an error"), which prevents an agent from misreading an empty result as a fault. It stops short of describing pagination or ranking tie-breaking, so it is strong but not exhaustive.

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 purpose, then alternatives, then the return shape, so an agent can stop reading early. The middle sentences are long and clause-heavy (the tools/description-vs-categories sentence in particular), costing some readability, but nearly every clause carries information an agent needs.

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?

There is no output schema, so the description carries the full burden of explaining the return value, and it does: results[] ordered best-first with named fields, plus searched and remaining-match counts. Combined with the freshness, cost, and empty-result notes, an agent can call this and interpret the response without further context.

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 baseline is 3, but the description adds genuine meaning: the query is matched against tools an agent returned and the description it wrote on-chain, and `hireable` is glossed as "whether it answered with a price when asked" — the same semantics as the returned escrow flag. The `speaks` and `limit` parameters are left entirely to the 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?

States a specific verb and resource — search ERC-8004 AI agents on BNB Smart Chain by task in plain words — and immediately narrows the corpus ("every ERC-8004 agent that actually answered when contacted", "not self-reported categories, not a curated list"). That qualifier makes it distinguishable from a catalog-style sibling at a glance.

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?

Gives an explicit when-to-use ("Use it before assuming no agent exists for a task"), a named exclusion (the four DeFi jobs — rebalancing, grid-trading, yield-optimization, health-factor — go to bnb_agents_by_evidence for track-record ranking), and a follow-up step (bnb_agent_chart to check one result before hiring). Alternatives and their selection conditions are spelled out rather than implied.

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