search_local_maps

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

No annotations are provided, so the description carries the full burden. It discloses cost (~1.5 points, ~5s) and zoom-level behavior tips. It does not mention authentication or data freshness, but the read-only nature is implied. The description is transparent enough for safe usage.

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 structured with clear sections (Use when, Don't use, Returns, Pair with, Cost, Tips) and uses bullet points. However, it is somewhat verbose with Chinese-English mix and some repetition (e.g., '本地商家搜索' appears multiple times). Still, it conveys information efficiently.

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?

Although no output schema exists, the description lists key return fields (place_id, name, about, etc.) sufficiently. It covers cost, zoom tips, and pairing with other tools. Missing pagination details, but given the parameter limit and return structure, the description is mostly complete.

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% for 6 parameters, but the description adds significant value: zoom levels explained with examples (1=world, 13=city, 21=building), default values clarified, and latitude/longitude examples given. The tips section further enhances parameter understanding.

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 specifies it searches for local businesses on Google Maps within a latitude/longitude range, returning detailed information like name, address, rating, and reviews. It differentiates from sibling tools such as amazon products and google_ai_search by explicitly stating the context (local business search).

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 description provides explicit 'Use when' and 'Don't use' sections with specific user queries and alternative tools. It names sibling tools like google_trends and google_ai_search, and advises on when to prefer them, making the usage boundaries clear.

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