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

With no annotations, the description carries the burden but only partially: it discloses the output type (ranked list + prose summary) and scope limitation ('covered areas'), but does not mention data freshness, ranking criteria, or any side effects. It adds some context but is not rich behavioral disclosure.

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 two sentences, front-loaded with the main purpose, then a usage statement. Every phrase adds value—ranking, prose summary, current area, and the targeted question type—with zero filler.

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 read-only discovery tool with six parameters and no output schema, the description gives enough context on scope, output, and the kind of question it answers. It could mention budget/audience filtering or more explicit behavior, but it is sufficiently complete for invocation decisions.

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 50%, so the description should compensate but only partially does. It relates 'time window' to the window parameter and lists example categories (theatre, concerts, tastings, festivals, tours) but leaves budget and audience unexplained, relying on their self-evident enums/names.

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 clearly states the tool provides 'Things to do in the covered areas' with 'ranked local happenings' and a 'citation-ready prose summary,' making the purpose unmistakable. It also differentiates from siblings like search_events by emphasizing ranking and prose output for 'what's on' questions.

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?

Explicitly instructs to 'Use this to answer "what's on / what should I do" questions about an area,' which provides a clear when-to-use signal. It does not name alternatives or state when not to use it, so it lacks the full 'when-not/exclusions' guidance for a 5.

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