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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the 'live stage information' return concept and current-time semantics, but does not explain timezone handling, how 'now' is determined, or what happens when nothing is playing. That is acceptable for a read-only tool but not especially rich.

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?

The description is compact and front-loaded: it states the core purpose first, then the return value, then example queries. Every sentence earns its place and there is no redundant restating of the tool name or 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?

For a simple read-only lookup with three optional filters and full schema coverage, the description and schema together give an agent enough to select and call the tool correctly. The return value is summarized, and there is no output schema to explain. A slightly deeper note on default scope when no filters are given would be the only meaningful gap.

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%, with each parameter described as a filter (city, event_id, event_week_id), so the schema carries the parameter documentation burden. The description does not add meaning beyond the schema, which puts it at the baseline of 3.

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 uses a specific verb ('Get') and a clear resource ('what's currently playing at festival/party events'), and immediately clarifies the return value: 'live stage information with current artists.' The 'now' emphasis cleanly distinguishes it from schedule-oriented siblings like get_event_schedule or get_event_details.

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 description gives explicit natural-language use cases: 'What's on now?' and 'Who's playing right now at AYA?' This tells the agent when to reach for this tool. However, it does not explicitly say when not to use it or mention alternatives such as get_event_schedule for future lineups, 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.