infomaniak_audit_dns_zones

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds valuable behavioral details: each domain requires 2 sequential API calls, default max_domains=20 keeps execution under ~30s, and the overall bulk-read nature is explained. No contradictions with annotations.

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 extremely concise: two sentences that clearly state the purpose and usage context. Every word adds value, with no filler or repetition of schema details. The front-loaded structure immediately conveys the tool's core functionality.

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 tool has an output schema (so return values are covered), three optional parameters with full schema descriptions, and detailed annotations, the description is complete. It covers purpose, behavioral traits (API calls, timing), and parameter tuning cues, leaving no critical gaps.

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%, providing baseline clarity. The description adds meaning beyond the schema by explaining the execution time implication of `max_domains` and providing an example for `filter_contains`. This additional context helps the agent make informed parameter choices.

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 performs a 'Bulk-read' of every domain owned by an account, returning DNS record counts and DNSSEC status. It distinguishes from sibling tools like `infomaniak_list_domains` or `infomaniak_dns_list_records` by focusing on a multi-domain audit with specific metrics.

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 explicitly marks the tool as 'useful for spot-checking large fleets', providing clear context for when to use it. However, it does not offer explicit guidance on when not to use it or mention alternatives, leaving some ambiguity for the AI agent.

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