create_batch

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

With no annotations, the description covers async behavior, independent operations, inclusion of destructive operations, respect for read-only/dry-run modes, and authentication/rate limits (max 10 concurrent requests).

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?

Well-structured with clear sections for purpose, usage, args, and return. Every sentence adds value without 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 no annotations, the description thoroughly explains behavior, parameters, return format, and constraints. Output schema exists but description still provides essential context.

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 single parameter 'operations' has 0% schema coverage, but the description fully explains it: JSON array with method, path, optional body, including allowed HTTP methods and example paths.

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 'Submit multiple API operations as a single asynchronous batch request' and differentiates from siblings by mentioning it's for bulk operations exceeding other tool limits like batch_subscribe max 500.

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?

Provides explicit context for when to use (bulk operations exceeding limits) and mentions polling with get_batch_status. Could be more explicit about when not to use, but guidance is clear.

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