dns_update_record

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

No annotations provided; description claims 'All fields are required' but schema shows TTL is optional, creating a contradiction. Does not disclose update behavior (e.g., partial vs full replacement, success/failure responses).

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?

Extremely concise (one sentence) but sacrifices essential information. While short, it fails to front-load critical details.

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?

Despite having an output schema, description lacks behavioral context, error handling, and usage scenarios. Inadequate for a tool with 6 parameters and 5 required fields.

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 0%; description adds no parameter explanations beyond a misleading statement about all fields being required. Does not clarify purpose of each parameter.

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 action ('Update a DNS record') and resource, but does not differentiate from sibling tools like dns_bulk_update_records or dns_create_record. The verb 'update' is specific enough.

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?

No guidance on when to use this tool versus alternatives (e.g., dns_bulk_update_records). Lacks context about prerequisites or when updates are appropriate.

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