manage_dns_forwarder_host_override_alias

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

The description states 'remove an alias', which is a destructive operation, yet annotations set destructiveHint=false. This is a direct contradiction. The description adds no further behavioral context beyond what annotations already claim.

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 one concise sentence, front-loaded with the action and resource. Every word earns its place, and there is no repetition of schema content.

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 schema richly documents parameters and an output schema exists, so the description doesn't need to explain return values. However, the annotation contradiction creates ambiguity about destructive behavior, and the description could have noted the confirm safety gate or create/delete parameter requirements, making completeness only barely adequate.

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 100%, so the baseline is 3. The description does not add any parameter-level detail, only a high-level summary of the operation. It neither compensates for nor detracts from the schema's rich parameter descriptions.

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 uses a specific verb ('Add or remove') and a clear resource ('an alias for a DNS Forwarder host override'). This clearly distinguishes it from sibling tools like create/update/delete host override or search 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?

The description provides clear context for when to use the tool (adding or removing an alias) but does not mention alternatives or exclusions. It omits explicit conditions for using create vs delete, though the schema hints at these.

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