batch_read

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions efficiency benefits, it doesn't describe critical behavioral traits such as error handling (e.g., what happens if some document IDs are invalid), performance characteristics (e.g., rate limits or size constraints), authentication requirements, or the format/structure of the returned data. This leaves significant gaps for a tool that performs batch operations.

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 extremely concise with only two sentences, both of which add clear value. The first sentence states the core purpose, and the second provides important usage context. There is no wasted language or redundancy.

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 the complexity of a batch operation tool with no annotations and no output schema, the description is insufficiently complete. It lacks information about return values, error behavior, performance limits, and other operational details that would help an agent use the tool effectively. The efficiency mention is helpful but doesn't compensate for these gaps.

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?

The input schema has 100% description coverage, with the 'documentIds' parameter clearly documented as 'Array of document UUIDs to read.' The description adds no additional parameter semantics beyond what the schema provides, such as constraints on array size or UUID format. Given the high schema coverage, the baseline score of 3 is appropriate.

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 the specific action ('Read multiple documents at once') and resource ('documents'), and explicitly distinguishes it from the sibling tool 'read_document' by noting it's 'more efficient than multiple read_document calls.' This provides clear differentiation from alternatives.

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 provides clear context for when to use this tool ('more efficient than multiple read_document calls'), which implicitly suggests using it for batch operations rather than individual reads. However, it doesn't explicitly state when NOT to use it or mention other potential alternatives beyond the named sibling.

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