batch_read

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

No annotations provided, but description details parallel execution via Promise.allSettled, read-only restriction, max 20 ops, and latency benefits. Adds behavioral context beyond basic function.

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 paragraphs plus a concise example. Every sentence is informative, no fluff. Structure is logical: purpose, constraints, usage pattern.

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?

No output schema, but the description indicates all results are returned. Could mention error handling or result format, but for a batching utility it's sufficiently complete.

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 100% with detailed description of operations array. The description reinforces structure with an example and max limit, adding value beyond 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 the tool batches multiple read-only calls, executes them in parallel, and returns results together. It distinguishes from siblings by being a batching tool for read-only operations, with explicit list of allowed tools in 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?

It specifies that only read-only tools are allowed and max 20 operations, with an example. Missing explicit guidance on when not to use (e.g., for single calls), but the context is clear.

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