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

readOnlyHint=true already tells the agent this is a safe read. The description adds that the response covers every run in the batch (an aggregate, not a single result), which is useful, but says nothing about pagination, partial/failed runs, or whether results are available before the batch finishes.

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 compact sentences, the primary purpose front-loaded and the API reference trailing. No filler; the endpoint mention is arguably redundant but harmless.

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 single-param read tool with annotations covering the safety profile, this is close to adequate, but with no output schema the description should give at least a hint of the return shape (per-run outcome, error handling), and it doesn't.

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?

Only one parameter with 100% schema coverage; the schema already documents the batch_id format (batch_...). The description adds the path mapping GET /api/v1/batches/{batchId}/results but no new constraints beyond what the schema gives.

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?

States a specific verb ('Fetch') and resource ('the outcome of every run in a batch'), backed by the exact REST endpoint. No sibling tool in the list deals with batches, so the agent can distinguish it from run-level reads like trigger_get_run, though the description never explicitly contrasts itself with those.

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?

There is no guidance on when to call this versus the many run-level siblings (trigger_get_run, trigger_list_runs, trigger_get_run_metadata). The phrase 'every run in a batch' implies a batch-scoped aggregation, but no prerequisite (batch must be complete), timing, or exclusion is stated.

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