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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds genuinely new behavioral context by disclosing the shape of the payload — ranked places with editorial notes — which is the only clue to return content since no output schema exists.

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, zero filler. The content definition is front-loaded and the usage hint follows, which is the right ordering for an agent scanning definitions.

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, fully-annotated read-only list tool with one documented parameter, the description covers what it returns and when to reach for it. Only minor gaps remain, such as whether all guides are returned when limit is omitted or how to page past the max.

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 a single optional parameter with 100% schema description coverage (default 20, max 50), so the schema fully carries the semantics. The description mentions nothing about limiting or pagination, so it adds no meaning beyond the schema; 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+resource (list curated editorial guides) and immediately disambiguates the content type — ranked 'best of' lists with editorial notes — which separates it from siblings like list_blog_posts or list_categories. An agent knows exactly what this returns without opening the schema.

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 best source for 'best X in this neighborhood' questions" gives a concrete triggering scenario and implicitly routes the agent away from search_places for editorial ranking queries. It stops short of explicitly naming search_places as the alternative or stating when not to use this tool (e.g., for a specific named place).

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