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

Beyond the annotations (which already declare read-only, idempotent and non-destructive), the description discloses data provenance and freshness (checked hourly from StubHub), price basis (per ticket, USD, before seller's fees), the presence of an event-page link in every result, and the priceCheckedAt freshness field. These are exactly the behavioral facts an agent needs but cannot get from the structured fields.

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 sentences, front-loaded with the core capability, then examples, then the result/refresh contract. No throat-clearing and every sentence carries distinct information (source, currency basis, use cases, output shape).

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 eight optional parameters and no output schema, the description does the heavy lifting well by describing what results link to and what priceCheckedAt means. It does not state what happens when the tool is called with no arguments at all (all params are optional), nor anything about result volume beyond the limit param, leaving a small gap.

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%, so the baseline is 3, but the description adds real meaning: it establishes that all prices are per-ticket USD before seller fees, which disambiguates what max_price actually filters on, and it clarifies that a page's price can be re-read live, explaining priceCheckedAt. It does not elaborate on the sort enum or date-range interplay beyond the schema wording.

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 opens with a specific resource and scope: live "from" prices for upcoming concerts, sport, theatre and festivals, sourced from StubHub listings via NeedATicket. The verb/resource pairing is unambiguous and the example queries pin down exactly what kind of question it answers.

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 stated concretely through example phrasings ("cheapest Oasis tickets", "what's on in Manchester next weekend"), which lets an agent pattern-match user intent to this tool. There are no sibling tools to exclude and no explicit "do not use for..." guidance, so it stops short of a 5.

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