pathgrove_count_stats

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that results are a fast approximation/overview rather than exact enumeration, which is useful, but it does not say whether counts are exact or estimated, nor how large a query it handles well.

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?

Two short sentences, front-loaded with the core action and followed by the rationale. No filler; only slight redundancy between 'statistics' and the second line.

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?

An output schema exists so return values need not be explained, and annotations cover safety. Purpose, scope and result shape are adequately conveyed; the only real gap is the accuracy of counts under the sampling mentioned in the schema.

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 description mirrors both optional behaviors ('count and size', 'breaks down by extension') corresponding to include_size and breakdown_by_extension, but adds no syntax or format detail for the query parameter. With declared schema coverage at 0%, this does not fully compensate, though the description at least signals what the optionals toggle.

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?

A specific verb and resource ('count and size statistics for files matching a query') tells the agent exactly what is produced. The clause 'without listing every file' implicitly distinguishes it from pathgrove_search, though no sibling is named explicitly.

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?

'Fast way to understand the scope of a query without listing every file' gives a clear use context and implies the alternative it replaces. It stops short of naming pathgrove_search or stating when-not to use it.

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