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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is added context — it delivers the sort order (best adjusted rating first), the fixed page size of 25, and that the response echoes available cities/lists with counts. It does not describe pagination limits or what happens past the last page.

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 dense sentences with the ordering and pagination facts front-loaded, then filters and response contents. No filler or restated title language.

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 no output schema, the description carries the burden of explaining returns, and it covers the ranking, page size, and the cities/lists-with-counts metadata. It leaves the shape of individual place entries unspecified, a minor gap for a browse 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 coverage is 100%, so the baseline is 3; the description adds real value by noting the page size of 25 (not in the schema) and by tying the city slug to the `cities` field of a prior response, which tells the agent how to discover valid filter values.

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 ('the ranked directory of places already analyzed for review fraud') plus the ordering rule and page size, which is enough to separate it from the single-place siblings like check_place and get_place_trust.

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 clear context for when this is the right tool ('what the site's home and city pages show') and signals discovery usage by noting the response lists available cities/lists with counts. It stops short of naming an alternative for the single-place case or stating when not to use it.

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