infomaniak_list_mailboxes

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

The description merely says 'list', adding no behavioral information beyond what the annotations (readOnlyHint, idempotentHint) already provide. No mention of scope, pagination, or performance implications.

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, which is concise but overly minimal, missing key contextual information about the parameter and usage. It is not front-loaded effectively.

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?

The tool is simple with one required parameter and an output schema, so the description is minimally adequate. However, it could be improved by linking to related tools (e.g., list_mail_hostings) and explaining the parameter's purpose.

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% (no description for the required mail_hosting_id parameter), and the tool description does not explain what this parameter represents, its format, or how to obtain it, providing no additional meaning beyond the schema.

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 action 'list' and the resource 'every mailbox on a given mail hosting', distinguishing it from sibling tools like infomaniak_get_mailbox_info which targets a single mailbox, and infomaniak_create_mailbox for creation.

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?

No guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., needing a mail_hosting_id from list_mail_hostings), and no context on when not to use it.

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