create_dns_record

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

Annotations already declare non-read-only, non-destructive, idempotent, open world. The description adds useful behavioral details: the tool is free (no credit cost) and returns the new record's id. No contradictions 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?

The description is relatively brief (3 sentences) with the main purpose upfront. It conveys necessary information without excessive verbosity, though the information about name and prio could be more integrated but is still clear.

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?

For a create tool with 6 parameters (3 required) and no output schema, the description covers key aspects: creation action, return value (id), cost, and important parameter nuances. It does not detail error handling or permissions, but given the rich schema and annotations, it is sufficiently complete.

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% with descriptions for each parameter. The description adds extra semantic guidance: explains name format (omit for apex, subdomain prefix only) and that prio is required for MX and SRV. This goes beyond the schema 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 starts with 'Create a DNS record on a domain', clearly specifying the verb and resource. It distinguishes from sibling tools by mentioning the returned id can be used by update_dns_record and delete_dns_record.

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?

Provides clear context for usage: explains when to use (to create a DNS record), gives specific instructions for the name field (apex vs subdomain), and notes that prio is required for MX/SRV. States it's free, which aids decision-making. Lacks explicit when-not-to-use mentions.

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