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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that: the data is merged from ticketing, sports and open-data feeds and refreshed every two hours, and each result carries a local date/time, venue, score with a one-line reason, and a link. It does not discuss the limit/truncation behaviour, but the provenance and freshness disclosure is substantial.

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?

A single front-loaded paragraph that leads with the core action and scope before ranking, coverage and examples. It is dense but each clause carries information; the result-shape sentence is partly redundant given the output schema.

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 seven optional parameters, an output schema, and read-only annotations, the description supplies what the structured fields do not: when to use the tool, the meaning of the ranking, data sources and refresh cadence, and example questions. An agent has everything needed to call it correctly without opening the schema.

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 the baseline is 3. The description adds meaning above the schema by explaining what the score driving "biggest" is (0-100 from expected crowd and timing) and by characterizing the query match (artist, team, show or venue), which helps the agent map natural-language requests onto the sort/query parameters.

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 verb and resource ("find events"), the scope (city, country, worldwide), the ranking basis (0-100 moment score or start time), and the covered event types. It is clearly differentiable from get_event (a single event) and list_cities (a look-up of supported places).

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 concrete usage context via example questions ("what's on in Lisbon this weekend", "when are Arsenal at home") and notes optional name filtering, which tells the agent when this tool fits. It stops short of explicitly naming when to prefer a sibling such as get_event for detail on one event.

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