infomaniak_list_vps

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds useful behavioral context by listing returned fields, noting it is 'Manager-private' (access restriction), and implying a safe read operation. No contradictions.

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?

Three sentences: first states the action, second enumerates return fields, third gives usage guidance. No unnecessary words, front-loaded, and each sentence serves a clear purpose.

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 output schema exists and annotations cover safety and idempotency, the description adequately covers purpose, return content, and workflow context. It does not mention pagination or filtering, but for a simple listing tool with one parameter, this is sufficient.

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 coverage is 100% with a clear description for `account_id`. The description does not add additional parameter semantics beyond what the schema provides, but it does hint at how the parameter is used (to later find a server by id). Baseline 3 is appropriate.

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 'List the VPS products of an organization' with a specific verb and resource, and distinguishes itself from the sibling tool `infomaniak_get_vps_full` by explaining the workflow (use this first to get an id). It also adds detail about Jelastic-managed and Manager-private.

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?

Explicitly advises to use this before `infomaniak_get_vps_full` to find a server's id. This provides clear contextual guidance. However, it does not mention when not to use it or any alternatives beyond the one sibling.

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