google_maps

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

No annotations provided, so description carries full burden. It discloses output format (ratings, prices, map screenshot) and default/max results. Lacks discussion of authentication, rate limits, or query limitations.

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?

Description is concise with a main sentence, sample prompts, and structured args. Every part serves a purpose without redundancy.

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?

No output schema, but description covers return types (ratings, prices, addresses, map screenshot). Parameters are explained. Missing some context like pagination or error handling, but sufficient for a search tool.

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 0%, so description adds crucial meaning: query is a place search query with examples, num_results has default 5 and max 10. The description explains both parameters effectively beyond the bare schema.

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 Google Maps for places, restaurants, businesses, and locations' and lists return data (ratings, prices, addresses, map screenshot). It differentiates from siblings like 'google_maps_directions' which is for directions.

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 example prompts that implicitly indicate appropriate use cases. However, it does not explicitly state when not to use or mention alternatives like 'google_maps_directions' for directions.

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