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

Annotations already declare readOnlyHint and destructiveHint=false, yet the description still adds real context: free, no key required, and critically that results are a dated snapshot of the last full read rather than a live call, with measured_at indicating recency. It also discloses that a provider with no sales returns zeros rather than an error. The only gap is return volume/shape beyond 'totals and top providers' and how 'top' is ranked.

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 but front-loaded: the core purpose comes first, then the credential/snapshot qualifiers, then sibling routing. Each sentence carries information, though the middle is packed tightly enough that a reader must parse carefully. No filler or repetition of the tool name.

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 one-optional-parameter read tool with no output schema, the description covers what is returned (totals plus top providers, or one provider's counts), the zero-result case, snapshot freshness via measured_at, and the absence of auth/cost barriers. Nothing an agent needs to call it correctly or interpret the result 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 single address parameter is already documented, including the 'provider address or agentWallet' distinction and omitting for the whole-kernel summary. The description reinforces the omit-for-summary behavior and adds the meaningful edge case that an address with no sales returns zeros, which the schema does not state.

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: counting providers who were 'actually been hired and paid' on BNB Smart Chain via the ERC-8183 job escrow, with the concrete pipeline (created, funded, delivered, escrow released) spelled out. It distinguishes itself from siblings by contrasting self-reported registration against funded jobs, so an agent can separate it from census/chart tools without opening schemas.

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 explicit routing: use this for the whole-kernel market view or one provider's totals, use erc8183_escrow_status for a job-by-job list of a wallet you hold, and bnb_agent_chart for a single hiring decision. Both alternatives and the selecting condition are named, leaving nothing to inference.

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