get_cities

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

No annotations are provided, so the description must fully disclose behavior. It mentions returning codes but does not specify result limits, pagination, error handling, or whether the operation is read-only. For a search tool with no annotations, this is insufficient.

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 compact, front-loaded with purpose, then usage guidance, then parameter list. No unnecessary sentences, and every line adds value.

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 purpose, parameter usage, and downstream integration with search_businesses. An output schema exists, so return values need not be detailed. For a simple search tool, this is largely complete, though lacking behavioral details.

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 0%, so the description must compensate. It explains each parameter (e.g., country_code is ISO 3166-1 alpha-2, keyword is city name or partial name), which adds meaning beyond the parameter names. However, the explanations are brief and do not cover all nuances like format or constraints.

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 'Search cities within a country by keyword' and specifies the use of returned codes in search_businesses filters. This verb+resource+scope distinguishes it from sibling tools like get_provinces or get_locations.

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?

Explicitly advises to always provide a keyword and never call without one, and explains how to use the results. However, it does not explicitly contrast with sibling tools or cover when not to use this tool.

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