Read Files (Batch)

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=true, so the safety profile is clear. The description adds the batch limit (20 files) and notes the same safety treatment as 'sdlc_read_file'. This expands beyond annotations without contradiction.

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?

Two sentences, front-loaded with purpose, no filler. Every word contributes meaning. Well-structured for quick parsing.

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?

Given a 5-parameter tool with defaults and an output schema, the description is minimal but covers the key constraint (batch of 20). It omits details on how 'path' relates to 'filePaths', caps on bytes/lines, and error handling. The existence of an output schema reduces the need to explain return values, but the description still feels incomplete for a 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?

Only 40% of parameters have schema descriptions, and the tool description adds no individual parameter details. It merely mentions the batch limit, which aligns with the 'filePaths' maxItems. The agent lacks guidance on 'path', 'maxBytes', 'maxLines', and 'redactSecrets' beyond defaults and constraints in the schema.

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 'Bounded batch read of up to 20 files', which specifies the verb (read), resource (files), and key constraint (batch of up to 20). It also references the sibling 'sdlc_read_file' for safety treatment, distinguishing this batch variant from the single-file 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 usage for batch reading but does not explicitly state when to use this tool versus alternatives like 'sdlc_read_file' or when not to use it. The reference to 'sdlc_read_file' provides a hint, but lacks clear direction on selection criteria.

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