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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only public search, but does not disclose authentication requirements, rate limits, pagination behavior, or how results are scoped. The nested payload also receives no behavioral explanation.

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 a single front-loaded sentence with no filler or redundancy. For a focused search tool, this is appropriately sized and immediately communicates the core operation.

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?

The tool has a rich nested schema and an output schema, so the description need not explain parameters or return values. However, it lacks usage guidance and sibling differentiation, leaving an agent to infer when this Google Maps search is preferable to related local-business or social search tools.

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 description coverage is reported as 100%, so the structured schema is expected to document parameters effectively. The description adds a small amount of meaning by mapping 'category' and 'location' to search_terms and location_query, but it does not explain optional parameters like limit, offset, max_places, or skip_closed_places.

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 gives a specific verb and resource: 'Search public Google Maps business listings' by category and location. This is clear and distinct from generic web search or social network searches, but it does not explicitly differentiate from the sibling tool 'local-business-data', which may cover similar territory.

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?

There is no guidance on when to use this tool versus alternatives such as local-business-data or other social-* search tools. The description states what it searches but not when it is the right choice or what its limitations are.

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