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

With no annotations provided, the description carries the full burden and delivers: read-only status, the hard 25-result cap, sort order, the presence of a total match count, and the exact per-result fields. It also warns that cities outside the covered set return zero matches.

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?

Front-loaded with identity and scope, and every sentence carries information (cap, ordering, fields, citations, routing). It is delivered as one dense block rather than scannable segments, which slightly hurts structure but not content economy.

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?

There is no output schema, so the description must describe returns — and it does, naming each field, the cap, ordering, and the total match count. Combined with the zero-required-parameter invocation model and sibling routing, an agent has everything needed to call and interpret this tool.

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%, so the schema already documents city slug/name formats, the free-text AND-matching behavior, and the 1–5 strength scale. The description largely restates the strength scale meaning rather than adding new parameter-level guidance, so the 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?

States a specific verb and resource (search a human-verified directory of 1548 NA venues) plus scope (70 cities across US/UK) and result semantics (max 25, sorted by NA Program Strength). It explicitly distinguishes itself from siblings by routing full records to get_venue and the covered city set to list_cities.

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?

Gives explicit conditions: all filters are optional, combine with AND, no filters returns top-rated overall, and when the total match count exceeds the cap the agent should narrow with filters. It also names the follow-up tools (get_venue by slug, list_cities for the covered set) with the reason to use each.

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