Collect Batch Results

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false, which is an unusual profile for a retrieval-looking tool. The description does not resolve the tension: it never says whether collecting consumes/removes the stored result, whether repeat calls fail, or what happens if the batch is incomplete. With annotations present but this ambiguity unaddressed, the description leaves real behavioral questions open.

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?

A single short sentence, front-loaded, with no padding. However, brevity here shades into under-specification rather than economy: the one sentence carries almost no actionable content, and "stored" adds no meaning.

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?

No output schema exists, so the description must convey what is returned, and it does not (result format, size, presence of per-point data). Against a batch toolset with submit_batch, get_batch_status, cancel_batch and summarize_batch as siblings, the description is too thin to place this tool correctly in the workflow.

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% for the single parameter batch_id, so the schema itself explains nothing. The description does not compensate: it never says what a batch_id is, its format, or that it comes from submit_batch. This is the one field the agent must supply and it is left undefined.

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?

"Return the stored batch result" names a verb and a resource, so the basic purpose is legible. But "stored batch result" is vague and the description gives no signal to separate this from the closely related siblings get_batch_status, summarize_batch, or submit_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?

There is no when-to-use guidance at all: no statement of the prerequisite (a batch must first be submitted via submit_batch), no indication of whether results are ready, and no named alternative such as get_batch_status for checking progress. The agent must infer the workflow entirely.

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