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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantive context beyond them: prices are refreshed hourly, are per ticket in GBP, exclude seller fees, results link out to the event page, and priceCheckedAt records last-read time. That freshness and price-semantics disclosure is exactly what an agent needs to avoid misrepresenting the numbers.

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?

Purpose and data provenance are front-loaded, followed by usage examples and return/link behavior. The final two sentences are slightly verbose but each carries real information (link destination, live refresh, priceCheckedAt), so nothing is wasted.

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, the description responsibly covers the return side (per-result link to the event page, priceCheckedAt field) and the freshness contract. Combined with a fully documented schema and safety annotations, an agent has everything needed to call and interpret it.

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 all eight parameters (including sort enum values and the anywhere default rule) are already documented in the schema. The description only loosely gestures at query/city/date through example questions and adds no syntax or format detail beyond it — 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?

States a specific resource (live "from" ticket prices) with explicit scope: upcoming concerts, sport, theatre and festivals, sourced from StubHub and checked hourly. An agent knows exactly what data this returns and at what granularity (per ticket, GBP, pre-fees).

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?

Gives three concrete example questions ("cheapest Oasis tickets", "what's on in Manchester next weekend", "how much are Metallica Sphere tickets") that map cleanly onto the query/city/date parameters, making the intended use case obvious. It stops short of stating when NOT to use it or naming alternatives, but there are no sibling tools to route away from.

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