combell_domains_set_renew

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

The description discloses the side effect of disabling renewal (letting the domain expire) and the precondition about can_toggle_renew. Annotations already indicate readOnlyHint=false, idempotentHint=true, destructiveHint=false, and the description adds context about the side effect and role requirement. 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 concise, front-loaded with the main action, and every sentence adds value: the action, the precondition, and the side effect. No wasted words.

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 covers the action, preconditions, side effects, and role requirement. It doesn't describe the return value, but there is no output schema and the tool is a simple boolean toggle. The only minor gap is not explaining what the response looks like, but for a setter tool this is acceptable.

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 50%: the will_renew parameter has a description ('true to renew automatically, false to let it expire'), but domain_name has no description. The description text adds context about the domain detail and can_toggle_renew, but doesn't explain domain_name format. Baseline 3 is appropriate since the schema covers half the parameters and the description adds some context.

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 action ('Enable or disable automatic renewal of a domain name') with a specific verb and resource. It distinguishes itself from sibling tools by focusing on the renewal toggle, which is unique among the domain-related tools.

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 states when the tool is allowed: only when can_toggle_renew is true on the domain detail, with specific conditions (no unpaid invoices, renewal not starting within a month) and the API user has the finance role. This provides clear guidance on when to use this tool versus alternatives.

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