get_batch_status

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

With no annotations, the description covers durability (batch IDs survive restarts), the status source, and output details. It does not mention permissions or side effects, but as a read-like operation, this is acceptable.

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?

Two sentences with no redundancy: first explains output, second adds behavioral detail. Highly efficient and front-loaded.

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?

Despite no output schema, the description explains the output format (states, rollup) and key behavioral trait (durability). Complete for a status retrieval 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?

The sole parameter batch_id is described in the schema, but the description adds context about durability. Since schema coverage is 100%, baseline is 3, and the extra context justifies a 4.

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 retrieves per-job status for a batch, listing specific states (pending/running/done/error/unknown) and rollup counts. It differentiates from the sibling get_job_status by focusing on batch context.

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 notes that batch IDs are durable and uses same status source as get_job_status, implying it should be used after submit_batch. However, it does not explicitly state when not to use it or provide clear alternatives.

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