Batch operations

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

The description claims read-only behavior, but annotations have readOnlyHint=false, creating a direct contradiction. Additionally, it does not explain how operations are specified or any error behaviors, leaving key behavioral aspects undisclosed.

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, no redundancy, and front-loaded with the core action. Every word adds value.

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?

Despite no output schema and no parameters, the description lacks details on how to specify the operations to batch, what happens on error, and any limits (e.g., max batch size). This leaves the agent with insufficient information to use the tool correctly.

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 no parameters (0 params), and schema coverage is 100%. Per guidelines, 0 params yields a baseline of 4. The description adds no parameter information because none exist.

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 executes multiple independent read-only operations in one call, which is a specific verb+resource. It further distinguishes itself from siblings by explicitly rejecting write or destructive operations, making its purpose unambiguous.

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 states when to use the tool (for multiple independent read-only operations) and what it rejects (writes/destructive operations). However, it does not explicitly name alternative tools or provide guidance on when not to use it beyond the rejection statement.

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