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

No annotations are provided, placing the burden on the description. The description lists exactly what statistics are returned, which is transparent about the core output. However, it does not explicitly state that the operation is read-only, nor does it disclose any data freshness or response shape considerations. With zero parameters, there is limited misuse potential, but the description could still be more explicit about safety and behavior.

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 verb and resource ('Get catalog statistics'), then efficiently enumerates the metrics. There is no waste, and every word contributes to understanding the tool's purpose.

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?

With an output schema present and zero parameters, the description fully covers what the agent needs to know for selection and invocation. The listed metrics align with what the output schema likely contains, and there are no missing prerequisites or edge cases to document.

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 zero parameters, and the schema reflects that with an empty object. Per the rubric, a baseline of 4 applies when there are no parameters. The description adds no parameter detail because none exist, which is entirely appropriate.

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 'Get catalog statistics' and enumerates the specific metrics (companies, projects, regions, categories, agent queries today, leads generated), making the tool's purpose unmistakable. This distinguishes it from sibling tools that fetch individual entities (e.g., get_company, get_regions) rather than aggregated counts.

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 the tool is for aggregate overview metrics, but it offers no explicit guidance on when to use this tool versus alternatives. For example, it doesn't mention 'use this for a high-level summary; use get_company for details,' so the agent must infer the distinction solely from the listed stats.

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