Find places on Google Maps

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

Beyond the read-only and open-world annotations, it discloses one-page pagination, the 20-place cap, conditionally available fields, and a three-credit charge per page regardless of result count. These details establish important output-scope and cost expectations before invocation.

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?

Three sentences front-load the purpose and usage triggers, then cover result scope, cost, and alternatives. The returned-field list is dense but relevant to tool selection, and there is no filler or redundant explanation.

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?

Together with the fully documented input schema, output schema, and safety annotations, the description supplies the triggers, scope, cost, pagination behavior, and sibling routing needed for correct selection and invocation. Details such as the location requirement for later pages and coordinate bounds are appropriately handled by the schema.

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%, and the schema already documents query behavior, pagination, location requirements, result limits, and per-page pricing. The description reinforces page and cost semantics but adds little new parameter-specific syntax or constraint information, making the high-coverage baseline of 3 appropriate.

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 opening sentence gives a specific verb and resource—finding local businesses and places on Google Maps—and identifies concrete use cases such as nearby options and lists with contact details. The final clause also distinguishes it from search for webpages and crawl for business-site content.

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 explicitly names three user intents that should trigger the tool: asking where something is, wanting nearby options, or needing businesses with contact details. It also routes webpage discovery to search and business-website reading to crawl, providing clear sibling alternatives.

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