group_statistics_locations

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

With no annotations, the description carries the full behavioral burden. It states the core behavior—returning item-count statistics grouped by location—but does not disclose output shape, how locations are identified, or whether any prerequisites exist. This is a reasonable but not deeply transparent description for a zero-parameter read tool.

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?

A single sentence that immediately states the operation and grouping criterion. It contains no filler, repeats no schema information, and front-loads the core meaning.

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?

For a no-parameter statistics tool, the description covers the essential invocation context. It lacks an explicit statement of the return format and does not clarify whether 'location' refers to the location tree, but these are minor for a tool with such low invocation complexity and no required inputs.

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 description has no parameter-specific burden. The baseline of 4 applies because there are zero parameters and thus no semantic gaps to compensate for.

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 uses a clear verb-resource pair, 'Get item-count statistics', and specifies the breakdown dimension 'by location'. This distinguishes it from sibling tools like group_statistics_labels and group_statistics_purchase_price, which clearly share the stats family but target different dimensions.

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 guidance is given for when to choose this tool over siblings. It neither mentions alternatives nor provides selection context, leaving the agent to infer usage solely from the name and the generic 'by location' phrase.

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