Buscar negocios en Google Maps

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

With no annotations, the description explains it returns specific fields (name, address, phone, web, rating, place_id) and mentions default and max results. No destructive behavior implied, but doesn't explicitly state read-only nature.

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 sentences, no filler. First sentence introduces main action with an example, second sentence summarizes filters and output. Every part is essential.

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?

Covers the main purpose, filters, and return data. Missing details on pagination or error handling, but given the complexity (6 params, no output schema), it 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?

Adds value beyond schema by providing example queries and explaining the purpose of the website_filter parameter. Schema already has 100% coverage, so baseline is 3; the description justifies +1.

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 it searches businesses on Google Maps using free text, and explicitly differentiates from siblings like get_business or get_reviews by focusing on search and filtering.

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?

Provides an explicit use case ('ideal para prospectar clientes') but does not mention when to avoid using this tool or alternatives beyond the implied sibling distinction.

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