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

With no annotations, the description carries the full burden and does disclose meaningful behavior: this is a public read, returns full content with temporal freshness and epistemic status, and supports 304-style optimization via client_hash. It does not cover not-found behavior or authorization edge cases, so it falls short of a 5.

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 compact and front-loads the core retrieval purpose, followed by behavioral caveats. The standardized protocol label and 'zero absolute truth assumption' phrasing add some jargon, but the sentence is still efficient.

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 tool with no output schema and no annotations, the description does enough to explain what is returned (full content plus freshness and epistemic metadata) and how client_hash affects fetching. It could be more complete by noting missing-item behavior or access expectations, but it is largely sufficient.

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 schema already documents all four parameters. The description adds a small amount of context for client_hash, but does not meaningfully clarify intent or ownerId beyond what the schema provides; baseline 3 is appropriate.

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 and resource: retrieve the full content of a knowledge item, rule cell, or invariant by ID. It distinguishes itself from search-style siblings by emphasizing exact-ID retrieval, though it does not name search_knowledge as the alternative.

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 description gives a clear usage hint for client_hash to avoid redundant re-fetching, but it does not explicitly say when to use this tool versus search_knowledge or other retrieval siblings. The by-ID scope implies the usage, but the guidance is not fully explicit.

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