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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds substantive context beyond them: the call mutates stored state by generating a venue list, and it spells out the filter criteria (busy, well-reviewed, no screen yet, unclaimed). It omits any auth/permission requirement, which keeps it from a 5.

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 the action and only two sentences, with no filler preamble. The venue enumeration is long but each item is doing filter-criteria work, so it is defensible rather than padding.

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?

An output schema exists, so return values need no explanation. The description usefully implies that an address or a lat/lng pair must be supplied even though the schema marks zero required parameters, which is an important disambiguation. It leaves unstated what happens when neither is provided and how a repeated call interacts with the previous 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?

Schema description coverage is 100%, so the schema already documents lat, lng, label and address. The description restates the address-vs-lat/lng alternative but adds no syntax, format, or precedence detail beyond the schema (e.g. what happens if both are supplied), 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?

Specific verb+resource: 'Set the area you are working' and it discloses the consequential side effect (building a suggested-venue list) rather than just the write. It also names the follow-up tool the agent should use to read the result, which separates it from the read-only siblings like ambassador.venues.list.

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 gives a clear workflow: set the area first, then 'read them with ambassador.suggestions.' That is real routing guidance. It stops short of a 5 because there is no explicit when-not-to-use and the referenced sibling name ('ambassador.suggestions') does not exactly match the actual sibling (ambassador.venues.suggestions), which could send an agent to a non-existent tool.

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