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

Beyond annotations (openWorldHint, destructiveHint: false), the description discloses that creation is synchronous and that the response includes a recordId, plus domain-specific constraints like CNAME being prohibited at the apex and SOA/apex NS being managed by GoDaddy. This gives agents realistic expectations of side effects and edge cases.

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 four focused sentences: purpose and non-destructive guarantee first, then naming rules, then type-specific requirements, then synchronization/response. Each sentence encodes distinct useful information without fluff or repetition of schema fields.

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 tool with 12 parameters and no output schema, the description covers the critical operational details: record-name relativity, TTL bounds, type-specific required fields, unsupported record placements, managed records, and the response including recordId. An agent has enough to call the tool correctly and interpret the result.

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?

Although schema coverage is 100%, the description adds high-value semantics: it defines the relative-name syntax, explains that MX/SRV require priority (SRV also port/weight), and notes CNAME cannot be set at the apex. This goes well beyond the individual property descriptions in the schema.

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 opens with a specific verb-resource pair ('Add a DNS record to a domain's zone') and immediately adds a distinguishing scope ('without touching existing records'), which separates it from update/delete/list siblings. It also explains the important naming convention ('@ = bare domain, www = www.example.com, * = wildcard'), leaving no ambiguity about what the tool does.

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 gives clear context by stating the tool adds new records without modifying existing ones, which implies its appropriate use case. It does not explicitly name sibling tools like update_dns_record or delete_dns_record as alternatives or state when to choose them, so it stops short of a 5.

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

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

The readOnlyHint annotation already declares the read-only nature, and the description reinforces it with 'Read-only; no payment method required.' It adds value beyond annotations by disclosing that pricing is indicative, per-term (registration/renewal), and converted from cents to whole currency units. 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?

Three short sentences front-load the primary function first, then add the read-only/payment guard, then the accuracy tip. Every sentence adds a distinct fact and there is no filler.

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 read-only check with 3 well-documented parameters and no output schema, the description conveys the core result domain: availability plus registration/renewal pricing in whole units. It does not specify the exact response structure, but the schema covers optimizeFor behavior and the tool is simple enough that the description is largely sufficient.

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 description coverage is 100%, and the schema already explains domains, iscCode, and optimizeFor (including the SPEED/ACCURACY trade-off). The description adds little beyond 'one or more domains' and a pointer to ACCURACY for a live check, so it mostly relies on the schema's detailed property descriptions.

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 opens with a specific verb ('Check') and resource ('whether one or more domains are available for registration'), making the primary function concrete. It also states 'Read-only; no payment method required,' which implicitly distinguishes it from registration, quoting, and suggestion 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?

The description implies usage context: it is a read-only pre-registration check with no payment required, and it advises 'Use ACCURACY for a live registry check.' However, it never explicitly names alternatives or states when to prefer this tool over list_domains, suggest_domains, or get_registration_quote, so routing between tools is left to inference.

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

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

Annotations already indicate destructiveHint=true and idempotentHint=false, but the description adds valuable context beyond them: the operation is permanent, verification is advised, and certain managed record types cannot be deleted. There is no contradiction with the 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 filler. The core purpose is front-loaded, followed by the irreversible warning and the managed-record exception. Every sentence contributes useful information.

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 two-param destructive tool, the description is complete: it states what is deleted, where the identifier comes from, why caution is needed, and what cannot be deleted. The annotations cover safety semantics, and no output schema is expected, so the absence of return-value detail is not a meaningful gap.

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 input schema fully documents both parameters with descriptions, including that recordId comes from list_dns_records and that deletion is irreversible. The tool description largely repeats that schema information rather than adding new parameter-level meaning, so the baseline 3 applies.

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 a specific verb and resource: 'Permanently delete one DNS record'. It also identifies the source of the recordId via list_dns_records, which distinguishes this tool from add_dns_record, update_dns_record, and list_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?

It gives clear usage guidance: verify the record first and understand that deletion is irreversible. It also excludes GoDaddy-managed SOA and apex NS records. However, it does not explicitly name update_dns_record as the alternative when the intent is to modify rather than delete, so it falls just short of a 5.

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

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

Annotations already provide readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds modest context by listing the returned fields, which is helpful because there is no output schema, but it does not disclose behaviors beyond that, such as behavior for nonexistent domains or permission requirements.

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?

A single, compact sentence that front-loads the core action and immediately lists the valuable return fields. There is no redundant or filler content.

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?

With no output schema, the description compensates by listing the key return fields. The single parameter is fully covered by the schema. It is complete enough for an agent to know what this tool provides, though it could briefly distinguish itself from check_domain_availability or list_domains.

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 description coverage is 100%, so the parameter is already fully documented in the schema. The description adds no additional parameter meaning, but none is needed given the schema's thorough explanation of the 'domain' field.

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 uses a specific verb ('Get') with a clear resource ('full details for one domain') and enumerates the exact data fields returned (lifecycle status, expiration, auto-renew, WHOIS privacy, transfer lock, nameservers). This clearly distinguishes it from list_domains and other 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?

The phrase 'for one domain' gives a clear context: use this when you need detail on a specific domain rather than a list of domains. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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

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

Even though annotations provide readOnlyHint=true, the description adds meaningful behavioral details: it locks the price to a quoteToken for a short window, returns required ICANN agreements, and explicitly states it does not charge the account. This is valuable context beyond what the annotations already convey.

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 three sentences with no wasted words. It front-loads the core purpose, then explains the key side effect and workflow position, making it easy to parse quickly.

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 no output schema, the description indicates the key returned artifacts (quoteToken and ICANN agreements) and explains the locking behavior and no-charge guarantee. For a two-parameter, single-required-field tool, this is complete enough for an agent to invoke it 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?

Schema description coverage is 100%, so the schema already documents both parameters (domain and period) adequately. The description adds minimal parameter-level meaning beyond the context of registering a domain, so a 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 uses a specific verb and resource: 'Get a price quote for registering a domain.' It clearly distinguishes itself from register_domain by explicitly identifying this as Step 1 of 2, so an agent can tell it apart from its closest sibling without opening the schema.

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 frames when to use the tool: as Step 1 of a two-step registration flow, with register_domain named as Step 2. It also clarifies that the tool is read-only and does not charge the account, which signals that it should be used before any actual registration mutation.

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

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

Annotations already mark the operation read-only, and the description adds context beyond that: records come from GoDaddy's authoritative nameservers, support type/name filtering, and include the recordId needed for mutations. 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?

Three short sentences front-load the main purpose, then add the most decision-relevant details: filtering and recordId. No filler beyond the acceptable one-word 'Read-only' summary, which reinforces the safety profile.

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?

The tool is a list operation with pagination parameters already documented in the schema, and the description covers the key return value (recordId) and the filtering model. There is no output schema, so a bit more detail about the response shape/pagination would help, but the existing details are enough for correct invocation.

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?

Input schema covers all parameters with descriptions, so the baseline is 3. The description mentions filtering by type and/or name and explains @ as zone apex, but this largely mirrors the schema and adds no deeper parameter semantics such as precedence or mutually exclusive combinations.

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 a specific action ('List DNS records'), a resource ('domain hosted on GoDaddy'), and a filtering capability, which distinguishes it from sibling tools like list_domains, add_dns_record, and update_dns_record. It also conveys that the result includes recordId for later updates/deletes, reinforcing its role.

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 tells the agent when the tool is useful by noting the recordId is needed to update or delete records and by stating filtering options. It does not explicitly preclude alternatives, but the read-only framing plus sibling context make the intended use clear.

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

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

Annotations already mark the tool as readOnlyHint=true, and the description reinforces this with 'Read-only.' It also adds the response field list and account scope, providing some extra context. However, it does not disclose pagination behavior, result ordering, or potential open-world breadth beyond the openWorldHint annotation.

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?

One sentence, immediately front-loaded with the action and resource, followed by a concise list of returned fields. No fluff or redundant explanation.

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?

The description is adequate for a simple listing tool, and the parameter schema covers pagination-related fields. However, with no output schema, the description could have mentioned pagination semantics (e.g., default page, how to use the token) or result sorting to be more complete.

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?

All 7 parameters have schema descriptions covering 100% of them, so the schema does the heavy lifting. The tool description does not add parameter-specific meaning, so the 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 states a specific verb ('List'), a specific resource ('domains owned by the GoDaddy account'), and enumerates the returned attributes. This clearly distinguishes the tool from siblings like get_domain (single domain) and list_dns_records (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 the use case: list all account-owned domains with details. However, it does not explicitly mention when to prefer this over get_domain (single domain lookup) or other sibling tools. The guidance is sufficient but not directive.

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

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

Annotations already flag destructive and idempotent behavior, but the description adds critical non-obvious details: it charges the billing method, is irreversible, requires explicit user consent, and runs asynchronously with a ~90s wait. This goes well beyond the structured 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?

Three sentences, all essential: the billing action and irreversibility are front-loaded, followed by prerequisites and async behavior. No redundant or filler content; every sentence adds decision-relevant information.

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 destructive, side-effect-heavy tool with 7 parameters and no output schema, the description covers the critical risks, prerequisites, and execution behavior. It does not describe the response shape, but the async acceptance model is disclosed, which is the most important contextual gap.

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 description coverage is 100%, so the schema already documents each parameter thoroughly. The description adds some useful context around the quote flow and price locking, but does not need to compensate for missing schema metadata. Baseline 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 states a specific action ('Register a domain') with a clear resource and prerequisite source ('using a quote from get_registration_quote'). It also clearly distinguishes this from related sibling tools by highlighting that it charges the account, is irreversible, and is the execution step after quoting.

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 gives explicit usage conditions: only after explicit user confirmation, requires a payment method and registrant contact, and should follow get_registration_quote. It does not name sibling alternatives explicitly, but the context makes the decision boundary clear for an agent.

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

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

Beyond the destructiveHint annotation, the description explicitly discloses that the action 'CHARGES THE ACCOUNT's billing method and cannot be undone.' It also gives a prerequisite: 'The account must have a valid billing method on file.' This adds meaningful behavioral context beyond the 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 four concise sentences with no filler. It front-loads the action, then covers costs, irreversibility, confirmation, and prerequisites in a logical order. Every sentence carries necessary information.

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 low-complexity tool with only two parameters, the description covers the essential prerequisites, billing impact, irreversibility, and confirmation requirement. It does not describe return values, but with no output schema and a simple renewal action this is a minor omission.

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 description coverage is 100%, so the schema already documents both domain and period well. The description restates the default period of 1 and the billing effect, but adds little new parameter-level meaning beyond what the schema already provides.

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 uses a specific verb and resource, 'Renew a domain', which clearly identifies the operation and distinguishes it from siblings like register_domain and get_domain. Adding 'for the given number of years' further clarifies the core action.

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 provides clear context for use: renewing an existing domain and requiring user confirmation before the renewal. It doesn't explicitly mention alternatives such as register_domain for new domains, but the prerequisites and confirmation requirement make the appropriate usage reasonably clear.

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

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

Beyond the destructiveHint annotation, the description discloses that propagation is asynchronous and that the tool waits or reports in-progress status. It also warns that moving nameservers off GoDaddy will stop serving existing DNS records, which is essential behavioral context for a destructive operation.

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?

Three sentences with no filler: purpose, async behavior, and critical warning are all front-loaded and concise. Every sentence earns its place.

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 destructive tool with a clear schema and no output schema, the description covers purpose, behavior, blocking semantics, and consequences. An agent has enough to invoke it correctly and set expectations for the result.

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 description coverage is 100%, so the schema fully documents both parameters, including the 2-13 count constraint and full-set replacement semantics. The description reinforces these points but does not add meaning beyond what the schema already provides.

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 a specific action—"Replace the authoritative nameservers for a domain"—with a concrete resource and count constraint. It implicitly distinguishes itself from the sibling DNS record tools by warning that those records will no longer be served after the change.

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 provides clear context: this tool changes delegation at the registry level, not individual records. It warns against use when GoDaddy DNS management is still desired, implicitly differentiating it from update_dns_record and related siblings, though it does not name alternatives explicitly.

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

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

The annotations already mark the tool read-only, and the description restates 'Read-only.' It adds some useful behavior: results are 'available' suggestions with 'indicative pricing' rather than guaranteed registrations. However, it doesn't disclose suggestion-source behavior, ordering, or whether results are exhaustive, so context beyond annotations is thin.

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 very short and front-loads the core purpose, but the standalone 'Read-only.' sentence repeats the readOnlyHint annotation and does not fully earn its place.

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 6-parameter read-only tool with no output schema, the description gives a clear one-line purpose and a hint at pricing in the response, but it omits output shape and does not route users away from semantically adjacent tools like check_domain_availability. Adequate, but with gaps.

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 description coverage is 100%, so the schema carries detailed meanings for query, tlds, sources, pageSize, lengthMin, and lengthMax. The description only restates the 'keyword or natural-language query' concept and adds no parameter-level guidance beyond the schema.

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 opens with a specific action and resource: 'Get available domain name suggestions for a keyword or natural-language query.' This clearly distinguishes it from siblings like check_domain_availability (checking a specific domain) and list_domains (listing owned domains).

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 the tool is for query-driven suggestion generation, but it never states when to prefer it over sibling tools such as check_domain_availability, nor does it mention any exclusions. Agents must infer the boundary from the tool name and sibling set.

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

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

Annotations already signal destructiveness, and the description adds a crucial behavioral detail: this is a FULL replacement where omitted fields are not preserved. It also discloses protected record types (GoDaddy-managed SOA and apex NS) that cannot be replaced, which is exactly the kind of behavioral context an agent needs before invoking a destructive 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?

Three sentences with no filler. The primary action is front-loaded, the full-replacement requirement is stated next, and the protected-record restriction closes the description. Every sentence earns its place.

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 destructive annotation and rich input schema, the description covers the essential operational context: how to identify the target record, the all-or-nothing replacement semantics, and the records that cannot be touched. No output schema exists, but the description does not need to detail return values for a PUT mutation.

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%, so the schema already documents all 13 parameters with type-specific meanings. The description reinforces that name, type, data, and ttl must all be supplied, which is redundant with the required array. It adds minimal semantic value beyond the schema, though the 'omitted fields are not preserved' note is mildly informative.

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 uses a specific verb ('Replace'), identifies the resource ('existing DNS record'), and pins the target via 'recordId from list_dns_records'. It clearly distinguishes this tool from add_dns_record and delete_dns_record by framing it as a full replacement operation.

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 makes clear this is for replacing an existing record, and the sibling list makes alternatives obvious. It explicitly excludes GoDaddy-managed SOA and apex NS records, but does not explicitly tell the agent when to prefer add_dns_record or delete_dns_record instead. The usage context is clear, but exclusions are partial.

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