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

Annotations only say non-read-only, non-destructive, open-world. The description adds substantive behavior: it expires the Stripe checkout link so it can't be paid, releases the waiting plan, its price against the spending cap, and the cap increase, charges nothing, and leaves the cap unchanged. It also states the return value (canceled plus the updated receptionist_service view).

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?

Prerequisites are front-loaded before the condition, and every clause carries information (what is expired, what is released, what is not charged). It is a dense single run-on sentence plus two short follow-ups, so structure is good though slightly heavy to parse in one read.

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 zero-parameter mutation with no output schema and partial annotation coverage, the description covers prerequisites, effects, cost implications, side-effect cleanup, the correct alternative for paid plans, and return values. Nothing an agent needs to invoke it correctly is missing.

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?

The tool takes zero parameters, so the description carries no parameter burden and the baseline is 4. The definition correctly implies no arguments are needed beyond the pending checkout state identified from receptionist_checkout.

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 and resource: cancel an unpaid plan checkout started via receptionist_checkout, expiring its Stripe link. It explicitly names the object it operates on (billing.pending_checkout in receptionist_service) and distinguishes the paid-plan case, so an agent can tell it apart from receptionist_checkout and receptionist_billing_portal.

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?

Gives a clear triggering condition ('when the owner decides not to pay a plan checkout started with receptionist_checkout'), a prerequisite ('Owners only, needs sign-in'), and an explicit alternative ('A paid plan is cancelled in receptionist_billing_portal instead'). When-to-use and when-not-to-use are both covered.

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