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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The '[PUBLIC READ/WRITE]' tag is ambiguous for a metrics query and does not clarify permissions, side effects, rate limits, or return behavior beyond a vague access label.

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 front-loaded sentence with no extraneous detail. The '[PUBLIC READ/WRITE]' tag is compact, and the core purpose is immediately clear.

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 zero-parameter stats tool, the description gives enough to know it returns cache metrics and hit rates, but with no output schema it does not describe the shape of the returned data. The lack of annotations also leaves behavioral completeness partially addressed by an ambiguous access tag.

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 zero parameters, so there are no parameter semantics to explain. The baseline for a no-parameter tool is a 4, and nothing in the description detracts from that.

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 states a specific verb ('Query') and resource ('metrics and hit rates of the active Key-Value Prompt Cache'), making the tool's basic function clear. It does not explicitly distinguish itself from siblings such as get_kv_cache_item or clear_kv_cache_memory, so it falls short of a 5.

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 implies that the tool is used for inspecting cache statistics, but there is no explicit guidance on when to choose it over get_kv_cache_item, clear_kv_cache_memory, or hvs_query_segregated_memory. Usage is only implicit from the tool name and description.

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