infomaniak_delete_site_alias

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

Annotations already flag the tool as destructive, but the description adds valuable behavioral details: 'Two-phase commit' and the post-condition that the Apache vhost will no longer respond. It also states the main FQDN exclusion. This goes beyond the bare destructive flag.

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, front-loaded with the primary purpose. Every sentence adds distinct information: action, exclusion, commit behavior, consequence, and access level. No filler.

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 description covers the main effect and constraint, and an output schema exists to describe returns. However, 'Two-phase commit' is mentioned but not explained, and there is no mention of the confirmation_token parameter or that list_site_aliases should be used first. This leaves gaps for a destructive operation.

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 only 25% (only alias has a description). The description reiterates the alias constraint but does not clarify hosting_id, site_id, or confirmation_token. With low schema coverage, the description should compensate, but it does not explain the remaining parameters.

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 states a specific action: 'Remove one alias FQDN from a web hosting site', which clearly identifies the verb and resource. It also distinguishes itself from siblings by noting the main FQDN cannot be removed, differentiating it from list/add alias tools.

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 provides clear context: it is for removing an alias from a hosting site, explicitly excludes the main FQDN, and notes the operation is 'Manager-private'. It does not explicitly name sibling tools as alternatives, but the scope is sufficiently clear.

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