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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, covering the safe read-only profile. The description adds one behavioral detail beyond annotations: results include event history. It does not disclose sorting, pagination, or how 'popular' is determined, so a middle score is appropriate.

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?

Two short sentences, front-loaded with the action and resource. The first sentence states the core behavior, the second justifies when it is useful; neither sentence is 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 simple read-only list operation with two fully documented parameters and safety annotations, the description is nearly complete: it covers city scope, the event-history detail, and the use case. It omits output format specifics, but no output schema exists and the tool is simple enough that this is only a minor 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?

The input schema documents both parameters with 100% coverage, including the default of 20 for limit. The description adds no extra parameter semantics beyond restating the city scope, which the schema already handles. Baseline 3 applies.

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 states a specific verb ('List'), a resource ('venues'), and a scope ('in a city'), adding a distinguishing detail ('with their event history'). It also frames the intended user value (finding popular venues or discovering new spots), which clearly separates it from the artist/event/city sibling tools.

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 sentence 'Use this to help users find popular venues or discover new spots' gives explicit when-to-use context. It does not mention alternatives or exclusions, but no sibling tool targets venues, so this guidance is sufficient without needing a when-not clause.

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