knowledge_get

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

With no annotations, the description carries the full burden of behavioral disclosure. It claims to retrieve 'full content', but the input schema includes a max_chars parameter that can truncate output, creating a potential contradiction between what the description says and the tool's actual behavior. The description also does not mention permissions, errors, or the safety of the read operation.

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 two sentences, front-loaded with the main purpose, and contains zero unnecessary words. Every sentence contributes meaning.

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?

While the tool is simple and the schema covers parameters, there is no output schema. The description only says 'full content' without explaining the return format or whether truncation can occur. It also does not clarify how this tool relates to siblings, leaving some contextual gaps for an agent.

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 baseline is 3. The description adds context for document_id by mentioning 'by its document ID' and for section with 'specific sections', but it does not explain max_chars beyond what the schema already provides.

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 clearly states the tool retrieves the full content of a knowledge document by ID, using the specific verb 'get' and the resource. It also mentions the ability to retrieve specific sections, which distinguishes it from sibling tools like knowledge_search and knowledge_list.

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 implies usage when you have a document ID and need its content, but it does not explicitly state when to use this tool instead of knowledge_search or knowledge_list. There are no explicit exclusions or alternatives mentioned, so guidance is only implied.

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