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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds behavior beyond that: results are ordered best-first, each carries rating/review count/distance/score, and a claim step is required before acting — context that meaningfully shapes how an agent uses the output.

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 tight sentences with no filler. The result shape and ordering are front-loaded, and the follow-up action is placed last where it belongs.

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 an output schema present, the description need not enumerate return fields, and annotations cover the safety profile; the description supplies the ordering and next-step semantics that structured fields don't. The only gap is the missing differentiation from ambassador.venues.list.

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 tool takes no parameters, so there is nothing for the description to disambiguate; per the baseline rule for zero-parameter tools this scores 4. The description does clarify that scoping comes implicitly from the caller's work location rather than an argument.

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 resource (venues suggested for your work location) and scope (best first), which is more precise than the bare name. It does not, however, distinguish itself from the closely-named sibling ambassador.venues.list, so an agent still has to guess which list to call.

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 one concrete workflow instruction — claim a venue via ambassador.venues.claim before approaching it — which is useful routing to a sibling. It says nothing about when to use this over ambassador.venues.list or advertiser.venues.search, so the primary selection decision is left implicit.

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