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

Annotations already flag destructiveHint=true, but the description adds the concrete consequence: turning it off cancels renewal and the domain expires at term end. It also discloses a confirmation boundary and idempotency expectations, adding value beyond the annotations. The 'every prerequisite stated above' reference is dangling since no such prerequisites appear in this definition.

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?

Purpose is correctly front-loaded and readable, but the canonicality, idempotency, and confirmation boilerplate is template-like and references details ('stated above', 'tool-specific retry key') not present in this tool's contract, diluting the signal.

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 mutation with annotations and no output schema, the description covers consequence, confirmation, and retry behavior adequately. The missing piece is any explanation of the _corply_context parameter and the undefined 'stated above' prerequisites.

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 0% with two parameters, so the description carries the burden. 'On or off' does give semantic meaning to the required boolean enabled. The _corply_context object with id and receipt is left completely unexplained in both schema and description.

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?

States a specific verb+resource: turning automatic yearly renewal of the company's Corply-registered domain on or off. An agent can identify the action unambiguously. It does not explicitly differentiate from adjacent siblings like clear_company_domain or start_company_domain_checkout.

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?

'Only when the founder asks' is an explicit usage gate, and it lists prerequisites (authenticated active company access). However, it names no alternatives and offers no when-not guidance for choosing between this and related domain tools.

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