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

With no annotations provided, the description carries the full disclosure burden and is unusually thorough: it discloses pricing, pilot protocol limits, unavailability of extra packs, the fact that inactivity does not pause billing, founding-member price protection, and that checkout/portal only return URLs to hand to a human. It also includes important guardrails about not handling payment details.

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 opening is front-loaded and the content is relevant, but the description is a single run-on paragraph with a large nested parenthetical packing pricing, protocol limits, withdrawal, cancellation, inactivity, and founding-member policy into one difficult-to-parse clause. It would benefit from clearer separation into shorter statements.

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 two-parameter tool with no output schema, the description covers action behavior, pricing, membership requirements, and important edge cases like pausing and founding-member pricing. The main gap is that the 'status' return value is not detailed beyond 'Membership status,' but this is partially inferable from the action enum and tool name.

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 schema already describes both parameters completely, so the baseline is 3. The description adds meaningful action-level semantics by explaining that 'checkout' returns a Stripe Checkout URL and 'portal' returns a manage/cancel URL, though it adds nothing about participant_secret beyond what the schema already provides.

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 identifies the tool as providing membership status or a payment-related link, and specifies that 'checkout' returns a Stripe Checkout URL and 'portal' returns a manage/cancel URL. It is clear about the resource and actions, but it does not explicitly differentiate itself from the sibling 'status' tool.

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 explicit guidance: searching/talking require membership, checkout should be used when a human needs to pay, portal is for managing or canceling, and billing pause requires an explicit withdraw rather than inactivity. It also states when not to act, such as never entering payment details and never raising membership without concrete justification.

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