Get a Calibrd pass

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

The annotations already signal readOnly and non-destructive behavior. The description adds useful operational context beyond that: the tool generates a checkout link rather than charging directly, externalizes payment to Stripe, and affects the daily report cap. No contradiction with the annotations exists.

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 sentences, each earning its place: the first defines the action and effect, the second clarifies payment mechanics, and the third gives precise call triggers. The description is front-loaded and contains no filler.

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 simple two-parameter tool with no output schema, the description is complete: it explains what is created, what the pass does, how payment works, where pricing lives, and when the tool should be called. 'Checkout link' sufficiently implies the return value for an agent.

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 baseline is 3. The description mentions the tier values (week, month, search) but does not add meaningful detail beyond the schema, which already explains durations and the currency default. The description therefore contributes little extra parameter semantics.

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: 'Creates a checkout link for a Calibrd pass', and clarifies the pass benefit ('removes the daily report cap and unlocks every tool'). The tier list (week, month, search) further distinguishes it from the sibling tools, which are about status, reports, scoring, and document review.

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?

Explicitly states when to invoke: 'Call it only when the person asks to buy, or after a tool said it needs a pass.' It also provides an exclusion by clarifying that payment happens on calibrd.com through Stripe, 'never in the chat', so the agent knows not to use it as a payment-processing tool.

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