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

With annotations already covering read-only and closed-world behavior, the description adds valuable operational details: a minimum polling interval and a cost guarantee ('No charge'). It does not describe error handling or rate-limit consequences beyond the 5-second rule, but the added context is meaningful.

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?

Three short sentences, front-loaded with the primary purpose, followed by two focused operational notes. No wasted words, and the most important information comes first.

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?

Output schema exists, so return values need not be explained. Annotations cover safety profile and the description adds polling and cost context. The main gap is the unexplained batch_id parameter and lack of sibling differentiation, but overall it is adequate for a simple read tool.

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 description coverage is 0% and the single required parameter batch_id has no description in the schema or the description. The description does not explain what a batch_id is, how to obtain it, or its format, leaving the parameter completely unexplained despite being necessary for invocation.

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 a specific verb and resource: 'Read batch progress and job IDs.' This distinguishes it from siblings like cancel_batch and get_job at a high level, but it does not explicitly name an alternative or clarify when to prefer get_batch over get_job.

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?

It provides a polling frequency constraint ('Poll at least 5 seconds apart'), which implies usage for progress monitoring, but it does not say when to use this tool versus alternatives such as get_job, nor does it mention prerequisites like authentication or batch ownership.

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