Ensure domain TXT verification

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

Beyond annotations (idempotentHint=true, openWorldHint=true), the description adds that it does nothing if the record already matches, does not wait for DNS propagation, and the response field 'resolved_domain' is the ASCII form. No contradiction 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 two sentences with no wasted words. It front-loads the core action ('align TXT record') and efficiently conveys conditions and side effects.

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 simple tool with one parameter and no output schema, the description adequately covers what it does, idempotent behavior, and a notable aspect (no wait for propagation). It is complete for effective usage.

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 single parameter 'domain' has a schema description covering 100% (Japanese domain support, automatic Punycode normalization). The tool description does not add further parameter details, so baseline score of 3 is appropriate.

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 tool's purpose: aligning the TXT record '_xserver-verify.{domain}' with the current domain validation token. It specifies the exact resource and action, and distinguishes from sibling tools like 'create_dns_record' which would generically create 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 usage for domain verification but does not explicitly state when to use this tool versus alternatives (e.g., 'create_dns_record', 'update_dns_record'). It lacks guidance on prerequisites or exclusion scenarios, though the idempotent hint and open world hint provide some context.

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