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

Annotations already mark this as a destructive write, but the description adds important side effects beyond them: a paused subscription is reactivated, one in dunning is taken out of dunning, and the customer is charged on the new date. It does not repeat idempotency or mention authorization requirements, but the key behavioral consequences are disclosed.

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 short, front-loaded with "WRITE:", and every sentence earns its place by covering purpose, constraints, side effects, and the endpoint. There is no filler or redundant restatement.

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 write with no output schema, the description supplies the essential context: the write nature, date constraint, reactivation/dunning effects, charge consequence, and endpoint. It omits explicit guidance on when to prefer sibling tools, but otherwise gives enough to invoke the tool 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 explains customer_id, subscription_id, and next_billing_date in detail. The description restates the date constraint but adds no parameter-level meaning beyond the schema, making the baseline 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 opens with a specific verb and resource: "WRITE: change when a subscription is next billed." This clearly distinguishes the tool from read-oriented siblings such as awtomic_get_subscription and awtomic_list_subscriptions, and the included endpoint confirms the 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 gives clear operational context: the date must be later than today, and paused or dunning subscriptions are affected. It does not explicitly compare this action to alternatives like awtomic_skip_next_order, awtomic_order_now, or awtomic_pause_subscription, so the when-not-to-use guidance is incomplete.

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