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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the shape of each result (time, venue, area, notes, and a link to cite), which matters because no output schema exists. It does not discuss empty-result behavior, rate limits, or result ordering.

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?

Three sentences, front-loaded with the core purpose, then usage examples, then the return shape. The category enumeration is long but each term is a genuine matching surface for user queries, so no sentence 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 usefully compensates by naming the returned fields, and all four parameters are fully documented in the schema. The main remaining gap is operational context such as pagination/limit interaction with the default of 30 or what a no-results response looks like, but nothing essential to correct invocation 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?

Schema description coverage is 100%, and the schema itself carries rich semantics for every parameter, including the UK-time / pre-4am "tonight" rule and the accepted area and type vocabularies. The description adds no parameter-level detail beyond what the schema already states, aside from the example queries that implicitly exercise area/type. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific verb ("List") and resource ("regular nights out and one-off events in Manchester, UK") and scopes it to a given date, with an explicit enumeration of categories (pub quizzes, comedy, open mics, live music, club nights, drag, happy hours). It is unambiguous about what the tool returns. However, it never names or contrasts with its siblings (get_venue, search_listings, seasonal_events), so sibling differentiation is left to inference.

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?

Three natural-language example queries ("what's on tonight in Manchester", "comedy in the Northern Quarter on Saturday", "quiz in Didsbury tomorrow") give a clear picture of the triggering intent and map directly onto the area/type/date parameters. There is no explicit when-not-to-use guidance and no mention of the alternative tools, 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.