serp_google_places

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

No annotations are provided, so the description carries full burden. It states it returns 'structured place results' but does not disclose behavioral traits such as authentication needs, rate limits, or the specific data fields returned. The input schema hints at pagination and localization, but the description adds no new behavioral context.

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 consists of two short sentences (20 words) that front-load the core purpose. Every word adds value; no fluff or redundancy. It is appropriately concise for a straightforward tool.

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?

Despite having an output schema (not shown), the description does not explain what 'structured place results' contain, such as names, addresses, ratings, etc. It lacks guidance on query specificity or result interpretation. For a tool with multiple optional parameters and a rich output, this is insufficient.

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% (all parameters have descriptions in the schema). The description does not add meaning beyond the schema descriptions; it merely reiterates that it searches for local places. Baseline of 3 is 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 description clearly states the tool performs a Google Places search for local places and businesses, and returns structured place results. The verb 'Search' and noun 'Google Places' are specific, and it distinguishes from siblings like serp_google_search and serp_google_maps.

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 implies usage for local business searches but does not explicitly guide when to use this tool versus alternatives like serp_google_maps or serp_google_search. No exclusions or when-not-to-use instructions are provided.

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