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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that access is public read and that the policies are foundational and forcefully injected, but it does not describe return format, size, or caching behavior beyond what the schema already says about client_hash.

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 a useful access tag and a compact enumeration of the policy categories. Every element 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?

For a simple read tool with one optional parameter and no output schema, the description is adequate: it identifies the content and public-read access. However, it does not describe the return shape or any operational details that would help an agent fully anticipate the response.

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?

Schema description coverage is 100%, so the single optional client_hash parameter and its 304 behavior are already fully documented in the schema. The description adds no parameter-specific semantics beyond that structured documentation.

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 uses a specific verb ('Inspect') and a specific resource ('foundational system policies'), and it enumerates the exact policy categories returned. This clearly distinguishes it from generic KV-cache retrieval siblings like get_kv_cache_item.

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?

It states '[PUBLIC READ]' and what the tool inspects, but gives no explicit guidance on when to use it versus alternatives such as get_kv_cache_item or query_kv_cache_stats. It also does not mention any preconditions or exclusions.

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