infomaniak_add_site_aliases

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

Description adds significant behavioral context beyond annotations: 'Two-phase commit', 'Asynchronous: returns a progress_id', and 'Manager-private'. No contradiction 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?

Three concise sentences with no redundancy. Key points front-loaded: action, wildcard support, two-phase commit, async nature.

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?

Explains prerequisites (DNS pointing), two-phase commit, and async result. Missing error handling details, but output schema likely covers return format. Sufficient for the complexity.

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 50%; description clarifies aliases parameter (wildcards, DNS prerequisite) and confirmation_token, but does not add meaning for hosting_id and site_id beyond what schema provides.

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?

Clear verb-resource pair: 'Bind one or more additional FQDNs to a web hosting site'. Distinguishes from siblings like delete_site_alias and list_site_aliases by specifying it adds aliases.

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?

States when to use: adding FQDNs to existing site, no provisioning. Mentions 'Two-phase commit' and async behavior, but lacks explicit when-not-to-use or alternative tools.

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