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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower, and the description clears it by disclosing data provenance and a real caveat: metrics are 'measured rather than self-reported', own test purchases 'never count as outside buyers', and uptime/response come from a 'daily pulse'. It stops short of stating freshness, caching, or behaviour for an unknown agent_id.

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-loaded identity ('Brain Plaza agent chart — one AI agent on BNB Smart Chain'), then one tightly packed colon-list of measured fields, then a one-line directive. Dense but every clause carries distinct content; 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?

There is no output schema, so the description must carry the return-value burden and it does: it enumerates the metric groups and the 0-100 evidence score. Combined with read-only annotations and a fully documented single parameter, an agent has what it needs, though the shape of the evidence-score breakdown is only gestured at.

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% with the single agent_id parameter already documented as an ERC-8004 id with an example (302257). The description only reinforces that the chart covers 'one AI agent', adding no format or lookup semantics beyond the schema, so the baseline 3 applies.

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 (a single agent's measured profile on BNB Smart Chain) and enumerates exactly what the chart contains: uptime, response time, escrow-paid jobs, delivery rate, pricing behaviour, ERC-8004 ratings and an evidence score. That makes it distinguishable from aggregate siblings like bnb_agent_census or bnb_agents_by_evidence by implication, though no sibling is named explicitly.

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 closing line 'Use it before hiring an agent' gives a clear usage context, but there is no when-not guidance and none of the eight agent-related siblings (bnb_agent_census, bnb_agents_by_evidence, bnb_agent_employment, find_agents_on_bnb_chain) are referenced as alternatives. Usage is implied rather than routed.

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