rmdns

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

No annotations are provided, so the description must convey behavioral traits. It merely states 'delete' without disclosing side effects, prerequisites (UUID must exist), or whether the deletion is permanent. This is insufficient for understanding implications.

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. For a tool with one parameter, this is efficient. However, a brief addition like 'requires UUID from dns output' would improve without sacrificing conciseness.

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 low complexity (1 param, no output schema), the description provides the core action. However, it omits that the UUID must come from dns output and does not describe return values or confirmation feedback, leaving gaps for the agent.

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%, so the parameter uuid is fully documented. The tool description adds no extra meaning beyond the schema, meeting the baseline. No parameter details in the description itself.

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 'Delete a DNS host override from Unbound', specifying the action (delete) and the resource (DNS host override). It distinguishes from sibling tools like mkdns (create) and dns (list).

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 implies use when needing to remove a host override but provides no explicit when-to-use, when-not-to-use, or comparison with alternatives. The parameter description hints at obtaining UUID from dns output, but the tool description itself lacks context.

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