get_geo

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

With no annotations, the description carries the full burden. It discloses the cascading behavior and how parameters affect results (e.g., country=US&region=California -> cities). It does not describe output format or error cases, but for a read-only discovery tool, the key behavioral trait is well covered.

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, information-dense sentence with examples. It front-loads the purpose and then provides a compact cascade illustration. No wasted words.

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?

For a tool with 3 optional params and no output schema, the description explains the cascade well. It does not specify the return shape or pagination, but the examples give enough context for an agent to infer the tool's behavior. Slight gap around what the final 'ISPs' output looks like.

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 only 33% (only country has a description). The description compensates by illustrating how all three parameters interact in the cascade (e.g., +city=Los%20Angeles -> ISPs), adding meaning beyond the schema. It falls short of fully specifying each parameter's possible values or formats.

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 opens with a clear verb+resource: 'Cascading geo discovery for proxy list targeting.' It distinguishes the tool from siblings by specifying a unique cascading behavior, and the examples clarify the exact purpose.

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 provides concrete usage patterns ('No params -> countries; country=US -> regions...'), which serve as implicit when-to-use guidance. However, it does not explicitly mention when not to use or compare with alternatives like search_proxies.

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