Get a WebAbility Pro payment link

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

Annotations mark this non-read-only and open-world, and the description adds real context beyond that: the link goes to a human, payment auto-activates the plan, card details never touch the agent, and an account/site prerequisite exists. It does not clarify whether each call mints a new link (non-idempotent) or how links expire, leaving a small gap.

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?

Front-loads the core action in the first sentence, then adds prerequisites and follow-up steps. Parentheticals ('the widget subscription', 'your owner') add clarity rather than waste, though the description could be tightened slightly.

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?

With no output schema, the description usefully explains what is produced (a Stripe Checkout link), what happens after payment, and how to verify with list_sites. It omits what an agent should do if the user declines or the link expires, a minor gap for a two-parameter tool.

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 documents 'domain' and the 'billing_interval' enum with its monthly default. The description reinforces that the link targets one specific site but adds no format or edge-case detail beyond the schema. Baseline 3 applies.

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: gets a Stripe Checkout link that places one site on the WebAbility Pro plan. It scopes the action ('one site') and names the sibling tools involved (add_site, list_sites), so an agent can place it in the workflow without opening other schemas.

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 clear context: hand the link to the human who pays, the site must already exist on the account (add_site first), and a free WebAbility account is required. It also points to list_sites to confirm activation. There is no explicit 'do not use this when...' exclusion, so it stays just short of a 5.

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