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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are restricted to venues with upcoming events and that each entry carries its GeNEVERsleep venue page URL, which is useful return-shape context; it says nothing about ordering, pagination, or empty-result behavior.

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 sentence with no filler. The phrasing 'with their GeNEVERsleep venue page' is slightly awkward but carries real information, so nothing is wasteful.

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 three fully documented optional parameters and no output schema, the definition covers the essentials but leaves the return shape only hinted at. For a discovery/list tool it is adequate without being thorough.

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%, including the city enumeration, lang default and limit range, so the schema does the heavy lifting. The description only reinforces that city is optional; it adds no meaning for lang or limit beyond what the schema states.

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?

Names the resource (clubs, bars, concert venues) and the qualifying scope (only those with upcoming events), with an optional city filter. It reads as a noun phrase rather than a verb+resource statement and does not explicitly distinguish itself from siblings like search_events, but an agent can still tell what it returns.

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?

The only usage signal is 'optionally in one city' implying the city filter can be omitted. There is no statement of when to pick this over search_events or get_event, and no prerequisites or exclusions are given.

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