list_batches

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

With no annotations provided, the description carries full burden. It clearly states read-only, safe to retry, and the max concurrent requests. It does not mention idempotency explicitly, but 'safe to retry' covers that. The description provides sufficient behavioral context for a simple list operation.

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 concise and well-structured: a one-sentence summary, alternative usage, authentication/limits, parameter details, and return format. 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?

For a simple list tool with 2 optional parameters and an existing output schema, the description covers all essential aspects: purpose, usage guidelines, parameter meanings, and return structure. It is complete and leaves no gaps.

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, so the description compensates by explaining both parameters: 'count' (1-1000, default 20) and 'offset' (pagination, use when total_items exceeds count). This adds meaningful semantics beyond the schema's type and default values.

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 'List recent batch operations with status and progress', specifying the verb (list) and resource (batch operations). It also distinguishes itself from the sibling tool 'get_batch_status', which provides 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?

Explicitly advises using 'get_batch_status' for detailed progress on a specific batch, providing a clear alternative. Also includes authentication via API key and concurrency limits (Max 10 concurrent requests), along with the note that it's read-only and safe to retry, guiding appropriate usage.

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