Read many text files

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the important behavioral idea that truncation is governed by byte budgets rather than lines, but omits what happens when the budget is exceeded, whether per-file failures abort the batch, and in what order results are returned.

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?

A single well-formed sentence with the verb and the differentiating mechanism front-loaded. Nothing is padded or repeated.

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 six-parameter batch tool with zero schema descriptions and no output schema, the description is far too thin: it says nothing about device targeting, concurrency, truncation signals, or partial failure semantics. An agent could call it, but could not predict its results.

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 carries the full burden, yet it only gestures at paths and the byte-budget parameters. concurrency, deviceId and deviceName — three of six parameters — have no meaning explained anywhere, and even the budget parameters get no guidance on defaults or interaction between maxTotalBytes and maxBytesPerFile.

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 and resource ('Read multiple UTF-8 files') plus the key scoping trait 'in one call', which separates it from single-file reads. It does not name a sibling (e.g. fs_read_chunk or read_multiple_files) explicitly, so differentiation is inferential 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?

'Using byte budgets instead of line limits' implicitly contrasts this with line-based read tools and hints that it should be chosen for batch reads, but it never names an alternative or states when not to use it. Usage must be inferred from a single clause.

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