infomaniak_list_ai_product_models

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds the 'OpenAI-compatible v2 endpoint' context, which is useful, but it does not disclose other behavioral aspects such as response format or potential errors. With annotations present, this adds modest value.

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, clear sentence that front-loads the action and scope. No redundant information, every word contributes.

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 low complexity (one parameter), strong annotations, and presence of an output schema, the description covers the essential purpose and scope. It could be enhanced by mentioning how to find the product_id or that this complements infomaniak_list_ai_models, but the current description is complete enough for a simple list operation.

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. The phrase 'one Infomaniak AI product' weakly maps to the product_id parameter, but it does not explain how to obtain or interpret the product_id, nor does it reference related tools. The parameter is simple, but the description provides minimal semantic enrichment.

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 lists models exposed by an Infomaniak AI product, using the specific verb 'List' and specifying the resource scope. It distinguishes itself from sibling tools like infomaniak_list_ai_products and infomaniak_list_ai_models by targeting models for a single product via its OpenAI-compatible v2 endpoint.

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 this tool is for when you need models specific to one AI product, but it does not explicitly state when to use it versus alternatives, nor does it mention prerequisites like obtaining a product_id from infomaniak_list_ai_products. Usage context is implied but not explicit.

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