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

Annotations already mark the operation readOnly, idempotent, and non-destructive, so the bar is lower. The description adds valuable behavior: per-entry independence, non-aborting failures for missing/oversized files, a cumulative 8MB budget, and the exact BATCH_BUDGET_EXCEEDED error.

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 two tight sentences with no filler. It front-loads the tool's purpose and batching scope, then packs constraints, failure behavior, and the error condition into the second sentence.

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?

Batching mechanics and budgets are well covered, and the output schema fills in return-value details. However, with zero schema parameter coverage, the unexplained optional parameters create a meaningful gap, and there is no advice about choosing this over sibling read tools.

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 must compensate. It explains the paths array and the cumulative byte cap, but it leaves maxBytesPerFile, name, and siteId entirely unexplained. An agent cannot know the meaning or effect of those optional parameters from either the schema or the description.

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 a specific verb ('read'), a resource ('editable source tree'), and a batching scope ('up to 50 paths'). It distinguishes itself from single-file read tools like read_source_file through the word 'Batched', though it does not explicitly name any sibling tool.

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 implies batch usage but never says when to prefer this over read_file, read_files, or read_source_file. There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives.

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