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

Adds substantial context beyond the annotations: the content is sold blind, each call costs $1 in USDC from the configured wallet, spend is bounded by per-call/session/daily caps, and returned data is third-party content rather than instructions. This explains both the non-read-only, non-idempotent nature (each call is billed) and a prompt-injection safeguard.

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, front-loaded sentences with no filler; the blind-purchase fact and the price lead, followed by billing mechanics and the third-party-data warning. Slightly dense but every sentence carries information an agent needs.

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 paid, no-output-schema tool with non-read-only annotations, the description covers cost, billing source, budget limits and data trust. Minor gaps remain — no mention of whether repeat calls yield different tips or what the tip payload looks like — but nothing critical 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?

There is a single parameter with 100% schema description coverage, and the schema already explains confirm_over_cap thoroughly (ignored for clients that can ask, never raises budgets). The description reinforces the budget-cap concept but adds no syntax or format detail beyond the schema, so the baseline of 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 concrete resource — a hand-written insider tip about ski season openings — and the commercial terms ($1 per call, product insider-info). It is clearly distinguishable from siblings like ski_prices or ski_coverage, though it never explicitly contrasts itself with them.

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: call this when you want a paid, blind insider tip. The description explains cost, USDC charging and budget caps, which shapes when it is safe to call, but it never states when to prefer an alternative sibling (e.g. ski_coverage) or when not to call at all.

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