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

With no annotations provided, the description carries the full burden. It discloses that the tool returns counts only, specifies what data is included and excluded, and mentions 'Live coverage' implying real-time data. It does not describe side effects, auth requirements, or rate limits, but for a read-only stats tool, the transparency is good.

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 is two sentences, front-loaded with the tool's purpose and key constraint ('Returns counts only'). Every sentence provides value: context, included/excluded data, and a usage statement. No wasted words.

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?

Given the tool has no parameters, no output schema, and no annotations, the description provides a thorough overview of what the tool returns (counts per chain, specific categories) and its use case. It could be more explicit about the exact output structure, but it is sufficient for a simple stats tool.

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 input schema is empty (0 parameters), and schema description coverage is 100%. The description correctly adds no parameter info since none exist. The baseline for 0 parameters is 4, and the description does not need to compensate further.

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 clearly states the tool returns 'Live coverage of the ERC-8004 agent economy' as counts only, specifying the chains (Base and Ethereum) and what is included (agents, MCP servers, OpenAPI, etc.) and excluded (no names, addresses, handles). It distinguishes itself from siblings like get_agent_summary by emphasizing aggregate counts rather than detailed agent info.

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 description explicitly says 'Use this to size the market and see where capability density is growing,' which provides clear context for when to use the tool. It does not explicitly state when not to use it or name alternatives, but the sibling tool names (get_agent_summary, get_leaderboards) imply that this tool is for aggregate stats, not detailed agent data.

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