Reset DNS Records

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool resets all DNS records to defaults, which implies a destructive and potentially irreversible operation, but it does not explicitly warn about data loss, mention whether the action can be undone (e.g., via snapshots), or clarify what 'defaults' means. This is a significant gap for a mutation tool.

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 that communicates the action, scope, and outcome without superfluous words. It is front-loaded and directly to the point, making it easy for an agent to parse quickly.

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 that this is a destructive tool with no annotations and no output schema, the description should provide more context. It does not explain what 'defaults' are, warn about the irreversible nature of the operation, or mention any related recovery options like dns_get_snapshots or dns_restore_snapshot. The description is too sparse for a tool that resets all records, leaving significant gaps in the agent's understanding of the operational impact.

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?

The only parameter, 'domain', is described in the schema with 'Domain name,' giving 100% schema description coverage. The tool description adds no additional meaning beyond the schema; it merely says 'for a domain,' which is already covered. Since schema coverage is high, the baseline of 3 applies, and the description does not add value beyond the structured data.

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 action ('reset all DNS records') and the target ('for a domain'), with the outcome 'to defaults.' It is easily distinguished from sibling tools like dns_update_records, dns_delete_records, and dns_get_records, which perform different operations on DNS records.

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 when to use the tool: when you want to reset DNS records to their default state. However, it provides no explicit guidance on when not to use it, no mention of alternatives (e.g., dns_update_records or dns_delete_records), and no prerequisites or caveats, so it only implies usage rather than offering clear usage context.

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