Performance Cache Stats

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

With no annotations provided, the description carries the full behavioral burden but only offers 'get'. It never states that this is a read-only, non-mutating operation, nor which cache backends are covered or whether results depend on cache configuration or warm state. The output schema covers the shape of the return, but nothing here discloses behavior beyond the schema.

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, front-loaded sentence with no filler or redundancy. It is appropriately tight, though the brevity leaves no room for the routing or context information an agent would benefit from.

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 with zero parameters the call surface is trivial. What is missing is what an agent needs to pick this over performance_redis_info or performance_memcached_stats and confirmation that the call is a safe read — enough to be adequate, not complete.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4.

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 gives a specific verb and resource (get + cache performance statistics), so an agent knows the operation type. It does not, however, distinguish itself from near-identical siblings such as performance_redis_info or performance_memcached_stats, leaving ambiguity about which cache layer is measured.

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?

There is no statement of when to use this tool versus the adjacent performance_* and cache_* siblings. No preconditions, no exclusions, and no alternative is named, so the agent must infer usage from the name alone.

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