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

Adds substantial context beyond the annotations: the content is unknown until paid, each call costs $1 USDC from the configured wallet, spend is bounded by budget caps, and the returned data is third-party and must not be treated as instructions. That last point is a valuable prompt-injection warning the annotations cannot convey.

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?

Four short sentences, front-loaded with what the tool returns and its blind-purchase model, then cost, then a safety note. No filler, though the fragments read staccato rather than as a single coherent guideline.

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 and a blind-sale design, the description covers the essentials an agent needs: cost, payment mechanism, budget limits, and the untrusted nature of the content. It could still say whether a failed/duplicate charge is refundable, given idempotentHint=false.

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 100% and the single parameter confirm_over_cap is fully documented in the schema itself, including the cap semantics and the fact that clients able to ask the user ignore it. The description only alludes to budget caps generally, so 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?

The description states a specific resource: a hand-written insider tip about ski season openings, and clarifies the unusual 'sold blind' delivery model. It is clearly not a data lookup like ski_coverage or ski_operator, though it never names a sibling explicitly.

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?

Usage is implied (buy a tip when you want insider knowledge) and the payment prerequisites are made explicit, but there is no when-to-use/when-not guidance and no routing to or away from alternatives such as ski_coverage or get_price_quote.

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