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

Annotations already indicate read-only, idempotent, and open-world characteristics. The description adds 'Live' which suggests real-time data, but does not elaborate on caching, update frequency, or any limitations. The behavioral transparency is adequate given the rich annotations but could be improved.

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 sentence, front-loaded with the key concept 'Live platform stats'. It is efficient and to the point, with no 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 the tool's simplicity (zero parameters, output schema exists), the description is largely complete. It lists the major statistics included. However, it does not clarify whether these are aggregated across all users or any other scope. The output schema likely fills in the gaps, so it's acceptable.

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 tool has no parameters, so the schema is fully covered. The description adds value by hinting at the output fields (entities count, countries, sources, homes published), which provides context beyond the empty schema. This is helpful for an agent to understand what the tool returns without inspecting the output 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 description clearly states the tool returns 'Live platform stats' and lists the specific data points (entities count, countries, sources, homes published). This distinguishes it clearly from sibling tools that focus on individual entities or specific lookups.

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?

No explicit usage guidance is provided. The description implies it is for obtaining overall platform statistics, but does not specify when to prefer this over tools like search_entities or get_full_dossier. The intended use case is understood from context but not articulated.

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