read_many_text_files

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

With no annotations supplied, the description carries the full burden, and it does disclose the key traits: read-only semantics, a hard cap of eight files, per-file byte bounds, and a requirement that paths live in approved roots. It does not say what happens when a path is missing, non-distinct, outside the roots, or when a file exceeds max_bytes_per_file (truncation vs. error), which leaves real behavioral gaps for a no-annotation tool.

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?

It is short and front-loaded, but the two sentences are near-duplicates — the opening claim about reading up to eight bounded UTF-8 files is repeated almost verbatim by 'Use to read up to eight existing UTF-8 files in one bounded, read-only call.' Only the 'approved roots' and 'own byte limit' clauses add new information.

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?

An output schema exists, so return values need not be explained, and the tool is a simple two-parameter read. However, with zero annotations the description should compensate for failure modes (missing file, path outside approved roots, more than eight paths) and truncation behavior; it does not, so it is adequate but not sufficient for a mutation-free yet error-prone batch operation.

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 both parameters are already documented inline with ranges and defaults (1 to 8192, default 8192). The description restates the distinct-path-in-approved-roots constraint without adding syntax, ordering, or duplicate-handling detail beyond the schema, so the baseline applies.

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 gives a specific verb and resource ('Read ... UTF-8 files') plus cardinality and batching scope ('up to eight ... in one MCP call'), which is enough to distinguish it from single-file siblings like read_text_file or read_text_page. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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?

'Use to read up to eight existing UTF-8 files in one bounded, read-only call' implies the batch-read scenario but gives no explicit trigger conditions, no exclusions, and no routing to alternatives such as read_text_file for a single path or read_text_page for partial reads. The agent can infer when it applies, but must guess about the boundary cases.

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