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

Annotations already mark this as readOnly and non-destructive, so the description's added value is its live behavior: it contacts ERC-8004 agents, checks whether they actually answer, and matches against the tools they return and their on-chain descriptions. It also sets expectations by rejecting self-reported categories and curated lists, which helps the agent interpret results.

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 opens with the core purpose and then adds methodology, expectations, and usage guidance in four short sentences. Each clause carries distinct information, and there is no filler or repetition.

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?

For a low-complexity read-only search with one required and one optional parameter, the description gives enough context to select and invoke the tool correctly: what it searches, how it verifies, and when to use it. No output schema exists, but the return behavior is implied by the purpose and the annotations cover the safety profile, so there is no material gap.

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 schema covers 100% of parameters, including query examples and the 'speaks' protocol constraint, so the baseline is 3. The description's phrase 'can do a given thing' mirrors the query parameter without adding syntax, formats, or validation beyond 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?

The first sentence states a specific action ('find') and resource ('AI agents on BNB Smart Chain that can do a given thing'), making the core purpose unambiguous. The second and third sentences sharpen the definition by describing the live-verification method and explicitly distinguishing this search from self-reported or curated lists, which separates it from related agent tools like bnb_agent_census and bnb_agent_employment.

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?

The last sentence provides explicit placement guidance: use this tool before assuming no agent exists for a task. It does not name sibling tools to use instead or state exclusions, so it falls just short of an explicit when/when-not/alternatives rule.

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