search_geo

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

No annotations provided, so description should compensate. It lacks any behavioral details such as whether the search is read-only, rate limits, pagination behavior, or what happens on no results. Extremely limited.

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?

Single sentence, no wasted words. Efficient for conveying the core purpose, but could sacrifice a bit of conciseness for more context.

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?

With no output schema and no behavioral transparency, the description is insufficient for agents to understand return format, pagination, or limitation. Sibling tools exist but no usage guidance is provided.

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% with parameter descriptions. However, the description adds no extra meaning beyond the schema; it merely repeats that the tool searches all types.

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 searches GEO for all record types, listing them explicitly. It distinguishes from sibling tools by using 'all types' versus their specific types.

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?

No guidance on when to use this tool versus more specific siblings like search_geo_series or search_geo_samples. Adding context like 'Use this for broad searches across all record types; use specific tools for targeted queries' would help.

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