create_dns_record

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

Adds critical human-approval gate and preview behavior beyond annotations. No contradiction; annotations (readOnlyHint false) align with mutation.

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?

Two succinct sentences conveying core functionality and key constraint, no wasted words.

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?

Adequate for a 9-param tool with no output schema; covers main action and gate. Could mention prerequisite (zone must exist) but that's in schema.

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 covers all 9 parameters with descriptions (100% coverage). Description only summarizes types and confirm role, not adding significant new meaning per baseline.

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?

Clearly states it creates DNS records and lists common types (A, AAAA, etc.), distinguishing it from update/delete/list siblings.

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?

Explicitly describes the confirm gate and preview mode, guiding when to use (with confirm true to execute). Could mention when not to use (e.g., for modifications) but context with sibling names suffices.

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