get_selection_result_tool

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

The description discloses that while the selection is incomplete, the tool returns a hint and can be polled repeatedly. This is useful behavioral context beyond the empty schema. No annotations are provided, so this description partially carries the transparency burden.

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, no redundancy. The first sentence states the purpose, the second adds the polling behavior. Perfectly concise.

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 zero-parameter polling tool with an output schema, the description covers the core workflow: it retrieves results and handles the pending state. It could mention prerequisites or error cases, but the description is adequate for the tool's simplicity.

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 tool has zero parameters, and the schema is empty. The description correctly omits parameter details. No parameter documentation is needed.

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's function: retrieving the result of a selection started with select_image_regions_tool. It uses a specific verb ('holt ab') and references the sibling tool, distinguishing it from other tools.

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 usage context: call after starting a selection with select_image_regions_tool, and call repeatedly while the selection is still pending. It doesn't explicitly mention when not to use it, but the intended workflow is clear.

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