renew_domain

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.