infomaniak_get_ai_batch_result

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering safety and idempotency. The description adds value by noting the asynchronous nature and the read/download modes, which inform the agent about two distinct retrieval behaviors. No contradictions with 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 a single sentence with clear front-loading of the action and resource. Every word earns its place, with no filler or redundancy.

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 simple 3-parameter schema and presence of an output schema, the description captures the core purpose effectively. It mentions asynchronous behavior, which is key, but could elaborate on batch completion requirements or the difference between read and download. Still sufficient for a read-only 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?

Schema description coverage is 0%, so the description must compensate. It adds meaning to the 'download' boolean ('Read or download') but leaves product_id and batch_id undefined beyond their names. This only partially addresses parameter semantics.

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 specific action ('Read or download') and resource ('result of an asynchronous Infomaniak AI model batch'). It distinguishes itself from sibling list tools (e.g., list_ai_products, list_ai_models) by targeting the batch result specifically.

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 implies usage for retrieving AI batch results but does not explicitly mention when to use this tool versus alternatives or provide exclusions. The asynchronous aspect hints at polling, but no concrete guidance is given.

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