fetch_businesses_statistics

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., if it's read-only, performance, or side effects). The schema hints at prerequisites but the description is silent.

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, front-loaded sentence that efficiently states the tool's purpose. However, it could be slightly more expansive without losing conciseness.

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 complexity of the filters (many parameters) and the absence of an output schema, the description is too vague. It does not enumerate all supported filter dimensions or explain the shape of the response, leaving agents underinformed.

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?

With schema description coverage at 0% (per context signal), the description must compensate but only vaguely mentions 'industry, revenue, employee count, and geographic distribution,' which hints at filter dimensions but adds little detail beyond the schema's own rich descriptions.

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 'Fetch aggregated insights into businesses by industry, revenue, employee count, and geographic distribution,' which includes a specific verb and resource. It distinguishes from siblings like 'fetch_businesses' which likely returns raw data, not aggregates.

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 does not provide any guidance on when to use this tool versus alternatives. While the schema contains usage notes about calling autocomplete, the main description lacks explicit when/why-to-use instructions.

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