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

The description adds value beyond annotations by explaining that each call runs independently with its own billing, returns per-call status/data/cost/duration, and that the batch wrapper is free. This clarifies behavior and cost implications not covered by readOnlyHint/destructiveHint/idempotentHint. No contradiction with annotations.

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 two sentences with no unnecessary words. Key details (limits, parallel execution, return format, pricing) are front-loaded and each sentence adds value. Emoji adds visual emphasis without bloat.

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 output schema exists (per context signals) and the input schema covers all parameters, the description provides sufficient context: concurrency limits, batching advantage, return structure, and cost model. No gaps for an agent to invoke 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?

Schema coverage is 100%, so the schema already documents both parameters in detail. The description does not add new information about parameters beyond what is in the schema, so baseline 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 tool executes up to 20 tool calls in parallel, with a specific action verb ('Execute') and resource ('tool calls'). It distinguishes itself from sibling tools that perform single calls by highlighting batching and concurrency.

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 explains when to use this tool (to reduce round-trips for multiple independent calls) with a concrete benefit ('Save 5x round-trips vs sequential calls'). It does not explicitly mention when not to use it (e.g., for dependent calls requiring sequential order) or list alternatives, but the context is clear enough for an agent to decide.

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