Read up to 50 files in a single call, with optional line ranges, to reduce separate file reads and gather code context.
Read up to 50 files in one call (strings, or {path,startLine,endLine}). Much faster than several read_file calls.
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | ||
| maxTotalChars | No |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one useful behavioral fact, the 50-file batch cap, but says nothing about truncation behavior or what happens when the output exceeds the default maxTotalChars of 150000.
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?
One sentence of capability plus one sentence of motivation, zero filler, with the batch limit front-loaded. Every clause 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 read tool with no output schema, the essential call shape is conveyed, but an agent is left guessing about maxTotalChars and about truncation when many large files are requested. Adequate but with a clear documentation gap on the second parameter.
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 0%, so the description has to carry the load: it does document the polymorphic file entry forms (string vs {path, startLine, endLine}), which mirrors the anyOf but gives an agent a usable summary. However, the second parameter maxTotalChars (default 150000) is never mentioned, leaving half the parameters undocumented.
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?
States a specific verb (Read) plus resource (files) with an explicit scope qualifier (up to 50 in one call). The contrast with the sibling read_file is implicit in the name and made explicit in the description, so an agent can distinguish the batch reader from the single-file reader immediately.
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?
It clearly positions itself against several read_file calls, which is a genuine routing signal (use this when you'd otherwise call read_file repeatedly). It stops short of stating when-not-to-use it (e.g. for a single file, or when output would exceed maxTotalChars), so it's clear context but no explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.