list_batches

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

Discloses important behavior: authenticated via API key, max 10 concurrent requests, read-only and safe to retry. This adds value beyond the absent annotations. Return format described in Args.

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?

Description is front-loaded with purpose, uses minimal sentences, and includes structured Args section. Every sentence is informative with no 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 tool's simplicity (list with pagination) and existence of output schema, the description covers purpose, usage, parameters, authentication, limits, idempotency, and return format. No gaps identified.

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 has 0% description coverage, but description explains both parameters: count (range 1-1000, default 20) and offset (pagination, use when total_items exceeds count). Adds concrete semantics missing from 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?

Description explicitly states 'List recent batch operations with status and progress' – clear verb+resource. Distinguishes from sibling get_batch_status by directing users there for detailed progress on a specific batch.

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 clear guidance: 'Use get_batch_status for detailed progress on a specific batch.' Also mentions authentication and concurrency limits. Lacks explicit when-not-to-use scenarios, but context is clear.

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