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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds a valuable behavioral guarantee: it never fabricates a checkout URL, ensuring accuracy. This goes beyond the annotations, which is meaningful for an agent relying on exact data.

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 description is two sentences with no filler. The primary purpose is front-loaded, and the second sentence adds a crucial reliability constraint. Every word earns its place; it's concise and well-structured.

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 tool with one parameter, no output schema, and annotations covering safety, the description is largely complete. It states what it returns (the exact link) and the precondition (known offer). It doesn't explain error behavior (e.g., what happens if the offer doesn't exist), but that's a minor gap given the simplicity and the read-only nature.

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 0%, so the description must compensate. It implies that 'id' is the identifier for a known CrossingKey offer, which adds meaning beyond the raw schema. However, it doesn't explicitly specify the exact nature of the id (e.g., internal offer ID vs. Stripe object ID) or its format, leaving some ambiguity. A more explicit mapping would be stronger.

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 states a specific verb ('Returns'), a precise resource ('Stripe Payment Link'), and a clear condition ('for a known CrossingKey offer'). It clearly distinguishes from siblings like list_stripe_offers (which lists offers) and get_request_credit_links (other link types). The 'Never invents a checkout URL' reinforces the exactness, making the purpose unmistakable.

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 implies the tool is used when you already have a known offer ID, and the 'Never invents' warning cautions against guessing URLs. However, it doesn't explicitly name alternatives or state when not to use it (e.g., 'use list_stripe_offers to find offers'). The context is clear but lacks explicit exclusions.

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