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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuine value by disclosing the shape of the returned content (tonight/weekend listings, parties, festivals, venues, genres), which matters because there is no output schema. It omits auth, rate limits, and pagination details.

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 compact sentence with no filler; the resource and slug source come first, followed by the content enumeration. The dense comma list is slightly hard to parse but every element conveys return-scope information.

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 only two parameters, full schema coverage, and rich annotations, expectations are modest and the description covers return content and slug provenance. It does not mention the locale parameter's effect on returned text/links, though the weak spot is the near-total absence of usage guidance and behavioral traits such as pagination or response format despite no output 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 coverage is 100% with examples ('berlin, paris, amsterdam') and the locale default documented, so the baseline is 3. The description pushes above that by adding cross-tool provenance for the slug parameter via list_cities, which the schema does not state.

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 identifies a specific resource (a city's page, keyed by slug) and enumerates the content it surfaces: tonight, weekend, parties, festivals, venues, genres. That is far more informative than the title alone, though it uses a noun phrase rather than an explicit verb and differentiates from siblings only indirectly via the list_cities reference.

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 parenthetical '(from list_cities)' gives a real chaining prerequisite, telling the agent to resolve the slug first. However, it never states when to prefer this over search_events or get_venue_events for the same city, and offers no exclusions or alternatives, so usage is largely implied.

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