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

The description explicitly states it is a 'read-only POST' that 'never modifies the user's zone,' aligning with the readOnlyHint annotation. It adds detail about return content (proposed records, TTL, provider-specific notes) and side-effect-free behavior, going beyond the annotation without contradiction.

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 somewhat lengthy but each sentence adds value (purpose, return details, when to use). It is well-structured without redundancy, so it remains efficient despite covering multiple aspects.

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?

No output schema is provided, but the description explains what the tool returns (proposed records, TTL recommendations, provider-specific notes). It also covers the workflow context (after identify problem, before verify). This makes it complete for an agent to use correctly.

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 description mentions all three parameters (domain, issue, context) and clarifies that context is 'from prior scan output.' While the schema already describes domain and context, the description adds the interrelationship (context for tailored output) and that issue is an enum; it does not enumerate the enum values but gives an example, which is adequate.

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: to generate copy-pasteable DNS record snippets that fix a specific issue, with an example (spf_missing → suggested SPF record). It distinguishes this from sibling tools like generate_spf or generate_dmarc by focusing on issue-based fixes.

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 explicit usage guidance: 'Use after explain_issue or scan_domain identifies a problem; use lookup_dns afterwards to verify.' This clearly tells the agent when to invoke this tool and what to do before and after, satisfying the 'when vs alternatives' criterion.

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