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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds behavior the annotations cannot convey: binary files are reported but never returned as text, and the byte budget causes files past it to come back unread, which changes how an agent must interpret results.

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?

Three short sentences, front-loaded with the core capability, then the recommended workflow, then the binary caveat. Every sentence carries information an agent needs and there is no filler.

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 read-only batch tool with no output schema, the description covers the essential call-site concerns: sequencing with files.tree, batching, binary handling and budget truncation. Only the semantics of the required `id` volume parameter and result shape are left unaddressed.

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 coverage is 67%, with paths and maxBytes already documented in the schema (including the default and the "unread" consequence). The description adds no further parameter detail and says nothing about the required `id` volume parameter, so it only marginally exceeds the schema baseline.

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?

"Read SEVERAL files in one call" gives a specific verb and resource and makes the batch-vs-single distinction explicit through "in one call" / "one call each." It stops short of naming files_read as the single-file alternative, so the differentiation is implied 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?

It prescribes a concrete workflow: use files.tree first to inspect layout, then batch-read only the handful of files actually needed in one round. That is clear when-to-use guidance, but there is no exclusion such as "use files_read when you need exactly one file."

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