infomaniak_list_site_aliases

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds useful context about the underlying Apache vhost/DocumentRoot setup, which goes beyond the annotations without contradicting them.

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 with no redundancy or filler. Each sentence adds value: action, context, and constraint. Very efficient.

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 that an output schema exists, the description does not need to detail return values. It explains what is listed (FQDNs) and the underlying architecture. It is complete for a listing tool, though the 'Manager-private' tag could be elaborated.

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%, and the parameter descriptions reference discovery tools (infomaniak_list_hostings, infomaniak_find_site), adding practical guidance beyond type definitions. The tool-level description does not add further parameter detail, but the schema itself is well-covered.

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 FQDNs (main + aliases) for a web hosting site, using a specific verb and resource. It distinguishes from sibling tools by mentioning that adding an alias is how you serve more domains, but the phrase 'Manager-private' is vague and not fully explained.

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 explains the purpose and context (serving multiple domains from a single WordPress install), implying when to use this tool. However, it does not explicitly state when not to use it or provide direct alternatives like infomaniak_add_site_aliases or infomaniak_delete_site_alias.

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