Set domain auto renew

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the bar is lower. The description adds valuable financial context—auto-renew charges the account and payments are non-refundable once confirmed—which is not present in structured fields.

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?

Two sentences with zero waste: the first front-loads the action, and the second adds the critical financial warning. 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 mutation tool with financial consequences, the description covers purpose and the key non-refundable charge warning. It does not mention permissions or the optional renewal_period_years behavior, but the schema covers the latter and the annotations cover the safety profile, leaving only minor 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 fully documents enabled, domain_id, and renewal_period_years. The description adds no parameter-specific syntax or format details beyond implying the target is an owned domain, making the baseline of 3 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 (Enable or disable) and resource (automatic renewal for an owned domain), clearly distinguishing it from sibling auto-renew tools like set_auto_renew or disable_vpn_auto_renew. An agent can identify the tool's scope 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?

Usage is implied by the purpose statement, but there is no explicit guidance on when to use this versus alternatives, nor any preconditions such as needing an owned domain or a payment method. The non-refundable warning hints at caution but does not function as usage guidance.

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