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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description goes beyond that by disclosing the timezone basis for results, the default time window, and the coverage failure mode (covered: false). It also states that every entry carries a source, which is a meaningful trust signal. It stops short of describing result ordering or pagination.

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 what the tool returns before the defaults and the coverage caveat. The long parenthetical category list is dense but earns its place by scoping exactly what counts as 'what's on'; nothing is redundant.

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 carries the burden of explaining returns and does so: a weekly schedule, dated events, a scene summary, a per-entry source, and a coverage flag. Combined with the local-time and default-window notes, an agent has everything needed to call it and interpret the result.

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%, so the schema already documents both parameters, which sets the baseline at 3. The description adds the important semantic that omitting 'day' yields tonight plus the coming week rather than a single day — a default the schema does not encode — but gives no extra help on the 'town' slug format.

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 the resource concretely — recurring nightly schedules (parties, live music, DJs, comedy, movie nights, games, salsa, markets, culture) plus upcoming dated events in a surf town — so an agent knows exactly what content comes back. It does not explicitly contrast itself with overlapping siblings like town_feed or social_posts, which keeps it from a 5.

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?

It conveys the default window ('tonight and the coming week, in the town's local time') and a real precondition ('some towns aren't covered yet (covered: false)'), which is useful context for deciding whether to call it. However, it never names an alternative tool or says when a different sibling (e.g. town_feed) should be preferred, so usage guidance is implied rather than stated.

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