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

With readOnlyHint=true, the read-only nature is known. The description adds that it returns sight count and web guide URL, and that omitting query lists all, which are useful beyond the annotations. However, it doesn't disclose pagination behavior or limit default, though these are partly in the schema. It adds some context but not rich detail.

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 two sentences, front-loaded with purpose, and includes a practical usage tip. Every word earns its place with no redundancy or fluff.

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?

The description covers the core purpose, return fields, and query behavior, but it doesn't explain the limit parameter (which lacks schema description) or clarify the interaction between query and country. It also doesn't mention result ordering or pagination. Given the tool's simplicity and existing annotations, this is moderate completeness with some gaps.

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 67% (query and country described, limit not). The description clarifies query use ('by name or country' and 'omit query to list all') but doesn't explain the limit parameter, which lacks a schema description. It adds some value but doesn't fully compensate for the gap.

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 states the tool finds Gingerguide cities by name or country, and specifies the return fields (sight count and web guide URL). This verb+resource+scope pattern distinguishes it from siblings like get_city_guide and list_countries.

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 provides clear context for usage: search by name/country, or omit query to list all. While it doesn't explicitly mention alternatives or exclusions, the usage scenarios are well implied. It lacks explicit when-not-to-use guidance but gives adequate context.

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