get_cache_stats

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

No annotations provided. The description implies a read-only operation by 'get', but fails to explicitly state it has no side effects, requires no special permissions, or that it is safe for repeated calls. The description does not disclose behavioral traits beyond the verb.

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?

Single sentence, no unnecessary words. Front-loads the core purpose and includes specific examples of returned data. Every word earns its place.

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?

No output schema, so the description must explain return values. It lists three key metrics, but does not specify the data structure (e.g., JSON object) or whether additional fields exist. Still adequate for a simple stats tool.

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?

No parameters, so the schema provides no information. The description compensates by listing example return values (hit rate, memory usage, performance metrics), giving the agent useful semantic expectations for the output.

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 the tool retrieves query cache statistics, specifying the resource (query cache) and the type of data (hit rate, memory usage, performance metrics). The name distinguishes it from sibling tools like 'get_stats' and 'clear_cache'.

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 on when to use this tool versus alternatives (e.g., 'get_stats', 'clear_cache'). The description does not mention prerequisites, when not to use, or context such as cache enablement.

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