KB Get Document

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

Annotations (readOnlyHint, idempotentHint) indicate safe, idempotent access. The description adds that expired documents are still returned with validity and freshness indicators, which is beyond the annotations. However, it does not specify behavior for non-existent IDs, leaving a minor gap.

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 well-structured: core purpose first, then expiration behavior, then verbose flag details. It is somewhat lengthy but every sentence adds value. No wasted words, but could be slightly more streamlined.

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?

Given the tool's simplicity (2 params, no nested objects, output schema present), the description covers retrieval purpose, expiration edge case, and verbose modes. It does not address error handling for missing IDs, but overall it is sufficiently complete for a read-only get-by-id 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?

Schema coverage is 100%, so baseline is 3. The description adds significant value: it gives ID format examples and explains the verbose parameter's impact on response fields (which fields are dropped/omitted, in_force behavior). This enriches the schema details.

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 explicitly states 'Retrieve a document by id' with concrete ID examples (STD-U-001, ADR-002). This clearly distinguishes it from sibling tools like kb_search (search) or kb_list (list). The verb 'Retrieve' and resource 'document by id' are specific and unambiguous.

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 explains that the tool always resolves regardless of expiry and details verbose mode behavior, but it does not explicitly state when to use this tool versus alternatives like kb_search or kb_list. No 'when-not' or 'use this instead of' guidance is provided.

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