directory_stats

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds content details (services, verification breakdown, data freshness) beyond the annotations. It does not contradict annotations, but it omits any potential side effects, performance characteristics, or required permissions—though these are less critical for a read-only stats endpoint.

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 a single, concise sentence that front-loads the main function and lists key data categories. Every word adds value, with no redundancy or filler.

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 no input parameters and no output schema, the description covers the essential information: it returns index-level stats about services, verification, and freshness. It could be enhanced by specifying the return format or exact fields, but the simplicity of the tool makes this adequate.

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?

There are no parameters in the schema, so the description has no burden to explain them. With 0 parameters, the baseline is 4, and the description appropriately focuses on what the tool returns rather than parameter details.

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 it provides index-level statistics covering services, verification breakdown, and data freshness. The resource (index) and data types are specified, and it distinguishes from sibling tools that focus on individual services or wallets.

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 implies usage for aggregate statistics ('index-level'), which contrasts with sibling tools for specific lookups, but it does not explicitly advise when to choose this tool over alternatives or mention exclusions. The writer expects the agent to infer from the context.

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