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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context such as 'areas belong to exactly one city' and the purpose of the returned vocabulary, but it does not describe response structure or any additional behavioral traits. This is acceptable but not exceptional.

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 front-loaded with the core action and then provides a detailed but purposeful list of returned content. The single sentence is dense, yet each listed item contributes meaning, and the closing usage guidance earns its place.

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 low-complexity tool with one parameter and no output schema, the description sufficiently explains what the agent will receive and when to call it. The enumerated return content plus the 'call before filtering' guidance makes the tool easy to invoke correctly without further research.

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?

There is only one parameter, slug, and schema description coverage is 100%, with the schema already explaining it as a city slug from list_cities. The tool description adds no additional parameter detail, so the schema carries the full burden and the baseline score of 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 clearly identifies the operation as retrieving a single city's guide and enumerates the key content (editorial blurb, venue count, filter vocabulary). It is unambiguous about the resource and scope, though it does not explicitly contrast itself with sibling tools like get_venue or search_venues.

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 phrase 'Call this before filtering' gives explicit, actionable timing guidance for when the tool should be used. It does not name alternative tools or state when not to use it, but the instruction is clear enough for an agent to sequence correctly.

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