get_batch_results

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

Annotations already provide readOnlyHint: true. The description adds that results are only available on specific job states and that they include text extracted from each response keyed by custom_id, which is valuable behavioral context beyond the annotations.

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 very concise: three sentences plus an args line. Every sentence is necessary and front-loaded with the purpose, with no extraneous content.

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 has an output schema, the description does not need to detail return values. It covers the single parameter, the valid states, and the nature of results. This is fully complete for a read-only result 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 input schema has no parameter description (0% coverage). The description explains that 'name' is the batch job name from create_batch, which adds critical context for the agent to correctly identify the parameter's purpose and source.

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 'Get results from a completed batch job', specifying the verb and resource. It distinguishes itself from siblings like get_batch (which likely retrieves job metadata) by focusing on results.

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 states availability conditions (state must be JOB_STATE_SUCCEEDED or JOB_STATE_PARTIALLY_SUCCEEDED) and indicates the name parameter comes from create_batch. Does not mention alternatives or when not to use, but the precondition is strong guidance.

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