get_chunk

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns the 'full content' of a chunk, implying a read operation. However, it does not mention error behavior, permissions, or any edge cases. For a simple fetch tool, this is minimal but acceptable.

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-loads the purpose, and contains no redundant information. Every word 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 1-parameter tool with no output schema, the description is sufficiently complete. It explains the action, the usage context, and indicates the return value ('full content'). It could mention not-found behavior, but the overall context is clear 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?

The schema provides no description for chunk_id (0% coverage), so the description must compensate. It adds context by stating this ID corresponds to a 'specific hit' from a search_docs call, which helps the agent understand where the ID comes from. It does not specify format or constraints, but with only one parameter, this is adequate.

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 'Fetch' and specifies the resource 'a single chunk by its ID', clearly distinguishing it from sibling tools like search_docs and search_code. It also states the purpose of retrieving full content for a specific hit, which is 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 explicitly provides a usage context: 'Use after a search_docs call to get the full content of a specific hit.' This clearly indicates when to use the tool. It does not explicitly mention when not to use it or compare with alternatives, so it falls short of a 5.

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