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

With no annotations, the description carries the behavioral burden. It clearly discloses the tool does not authorize or complete payment, which is critical safety context. The precondition about explicit buyer authorization also clarifies when the action is appropriate.

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?

Three dense sentences with no repetition or filler. The precondition is stated first, the core function second, and the alternative routing third, making each sentence earn its place.

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 single-parameter tool with no output schema, the description explains what it returns, when to use it, what not to do, and which alternative tools to use. Nothing essential for correct invocation 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?

Schema coverage is 0%, but the description connects the 'plan' parameter to the buyer's selection of Builder or Agency, mapping directly to the enum values. It adds process context beyond the raw enum, though it does not explicitly name the 'plan' parameter.

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: 'Returns the official Stripe checkout URL.' It also differentiates from siblings by explicitly saying it 'never authorizes or completes payment' and by pointing to get_leadproof_trial and get_leadproof_plan_decision for other situations.

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?

Provides explicit preconditions: use only after the buyer selected Builder or Agency and explicitly authorized a paid checkout. It also names alternatives when the buyer has not evaluated the product, giving the agent clear routing logic.

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