update-me-dns-record

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

Annotations indicate idempotentHint=true (the operation is safe to retry) and readOnlyHint=false (it's a mutation). The description adds the crucial behavioral detail that the operation is 'Mutating operation', which aligns with non-readOnly. It also specifies which fields are immutable, adding context beyond 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 two sentences: the first states the tool's purpose, the second provides immutable-field guidance. No wasted words; front-loaded with critical info.

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 the tool has no output schema, the description fully explains the operation, its constraints, and alternatives. For a mutation operation with clear parameters and annotations, the description is complete enough to guide correct use.

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% and descriptions in the schema are thorough, including formats, patterns, and constraints. The description adds no further parameter details but reinforces that only `value` and `priority` are mutable. Since schema already does heavy lifting, a 4 is appropriate for not repeating what's already covered.

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 states 'Update the value or priority of an existing DNS record' which is a specific verb+resource combination. It clearly distinguishes from siblings like create-me-dns-record (creation) and delete-me-dns-record (deletion), and lists the two mutable fields explicitly.

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 explicitly states when NOT to use this tool: if `fqdn`, `type`, or `ttl` need to change, the user should 'delete and recreate' instead. This provides clear guidance on when to use alternatives (create/delete) and outlines the immutable fields.

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