infomaniak_get_domain_resources

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safe read-only nature. The description adds the 'canonical v2' API context and enumerates resource types, but it does not disclose pagination, permission requirements, or response behavior beyond what annotations already provide.

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 front-loaded sentence with no redundant words. It efficiently communicates the core purpose without bloat.

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?

Although output schema and annotations are present, the tool is a multi-mode dispatcher with eight resource operations and four parameters. The description lacks guidance on operation selection, parameter dependencies, and how this canonical tool relates to the many specialized sibling tools, making it insufficient for reliable invocation.

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%, and the description does not explain any of the four parameters (resource, zone, domain, record_id). It only lists resource categories that loosely map to the resource enum, providing no meaningful parameter-level semantics.

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 reads canonical v2 domain, zone, DNSSEC, and DNS-record resources, specifying both the verb and the resource scope. However, it does not explicitly distinguish this from sibling tools like infomaniak_get_domain or infomaniak_dns_list_records, so differentiation is limited.

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 when-to-use or alternative guidance is provided. The phrase 'canonical v2' implies a preference for this read path, but the description never explains when to choose this tool over specialized siblings such as infomaniak_dns_list_records or infomaniak_manage_dnssec.

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