RAG MCP Tool

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Read raw content') but doesn't mention permissions required, file size limits, encoding issues, error handling, or what happens with binary vs. text files. This leaves significant behavioral gaps for a file I/O 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 extremely concise with zero wasted words. It states the purpose in one clear sentence, then provides parameter semantics in a structured format. Every sentence earns its place, and the information is front-loaded appropriately.

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 (one parameter) and the presence of an output schema (which handles return values), the description covers the basics adequately. However, for a file reading operation with no annotations, it should ideally mention more about behavioral aspects like permissions, encoding, or error cases to be fully complete.

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 description adds meaningful context for the single parameter by specifying 'Absolute path to the file', which clarifies the expected format beyond what the schema provides (schema coverage is 0%). This compensates well for the lack of schema descriptions, though it doesn't elaborate on path validation or OS-specific considerations.

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 verb ('Read') and resource ('raw content of a file'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from the sibling tool 'search_rag', which appears to serve a different function (search vs. raw reading).

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 provides no guidance on when to use this tool versus alternatives. While 'search_rag' seems different, there's no explicit comparison or context about when raw file reading is appropriate versus searching. No prerequisites or exclusions are mentioned.

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