infomaniak_list_sites

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint true, so the safe read behavior is covered. The description adds scope (given web hosting) and mentions applications are attached, but doesn't disclose pagination, ordering, or result size. It is consistent with annotations and adds limited behavioral context.

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?

A single, front-loaded sentence that communicates purpose and a clarifying parenthetical. No filler, no redundant content, and the structure is easy to parse.

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 simple list operation with one parameter, good annotations, and an output schema, the description is close to sufficient. It could be more complete by explaining how to obtain hosting_id or when to use this vs find_site, but the essential behavior is covered.

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 0%; the description doesn't explain the single 'hosting_id' parameter beyond saying 'given web hosting'. Since coverage is low, the description should compensate, but it doesn't clarify the parameter type, semantics, or where to find the ID. The param name is self-explanatory, which gives minimal added value.

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?

Description uses a specific verb 'Lists' and identifies the resource 'all sites on a given web hosting', with a parenthetical clarifying that attached applications are included. It clearly distinguishes from sibling tools like infomaniak_list_hostings (which lists hostings) and infomaniak_find_site (which finds sites).

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 the tool is for listing sites when you have a hosting_id, but provides no explicit when-to-use guidance, exclusions, or alternatives. It doesn't mention that infomaniak_find_site or infomaniak_list_hostings could be used for related tasks, so usage context is only implied.

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