search_geo

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

No annotations provided, so description carries full burden. Only mentions Apple's lowercasing quirk for countrycode. No disclosure of rate limits, auth requirements, or other behavioral traits.

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?

Extremely concise: two sentences that efficiently convey the tool's purpose and a key usage nuance. No extraneous information.

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?

While description covers basic search behavior, it lacks details on response format, pagination behavior (limit/offset are in schema but no usage context), and error handling. More context would help, given no output schema.

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?

Input schema has 83% description coverage (5 of 6 parameters described). Description adds value by clarifying Apple's case sensitivity for countrycode and noting v5 entity support. Beyond schema, it provides practical usage context.

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?

Description clearly states it searches geo entities by name, listing supported types. It adds context about the countrycode quirk. However, it does not explicitly differentiate from sibling tools like geo_lookup.

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 guidance on using countrycode to scope searches, but lacks explicit when-to-use vs alternatives or when not to use. No exclusion criteria for sibling tools.

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