stats

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

No annotations exist, so the description must convey behavioral traits. It indicates a read-only operation showing statistics, which is appropriate. However, it lacks information on whether the stats are real-time, cached, or require prior compression operations.

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 that perfectly captures the tool's purpose and output. No wasted words; every element (show, compression statistics, and the three specific metrics) is purposeful.

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 parameterless stats tool with no output schema, the description is complete. It lists exactly what the tool returns, and there is no missing information needed for correct usage.

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?

There are no parameters in the input schema, so no additional semantics are needed. The baseline for zero parameters is 4, and the description does not distract with unnecessary parameter details.

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 'Show compression statistics' and enumerates three specific metrics (total items stored, bytes saved, compression ratio). This verb+resource combination is unambiguous and distinct from siblings like 'list' or 'analyze'.

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 purpose is clear—use to retrieve compression stats. It doesn't explicitly list when not to use or contrast with siblings, but the simplicity of the tool makes alternatives obvious.

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