Batch read

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

Annotations only give readOnlyHint and openWorldHint, and the description adds real context: sequential execution, cache reuse for read/info, a response budget, and an ok/error envelope per item. It does not say what happens when one op fails (abort vs. partial success) and 'response budget' stays undefined, which is the main gap for a batch 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?

Front-loaded with the core capability, then labeled sections for usage, speed, and output — highly scannable with no filler sentences. 'Batch-safe: yes' is mildly redundant with readOnlyHint, but overall the text is tight.

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?

With two parameters at 0% schema coverage and no output schema, the description covers the output envelope shape but leaves the per-operation argument contract and the byte-budget parameter unexplained. Adequate for choosing the tool, incomplete for invoking it correctly on the first try.

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 carry the load; it names the allowed operation values but never explains the shape of `arguments` for each operation, nor what max_response_bytes_per_item does when exceeded. The 'up to 8' cap and the enum list only restate what the schema already encodes.

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 (run up to 8 read-only ops in one call) and enumerates the four permitted operations, which cleanly separates it from the single-op siblings like project_read_file and project_search. An agent can pick it without opening the schema.

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?

Explicit 'Use when' (2+ files/ops in the same step) and 'Avoid when' (single op, or mutating ops — use the corresponding tool) sections, with the alternative named rather than implied. That is the full when/when-not/alternative triad.

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