list_geo_targets

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

With no annotations providing safety or behavioral hints, the description must disclose behavior itself. It only says 'List all' and does not explain that pagination is involved via limit/offset, nor what happens if there are many targets. The schema hints at pagination, but the description fails to mention it, making the tool's behavior unclear for an agent.

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 redundant wording. It efficiently conveys the core purpose and includes a helpful parenthetical clarification without any fluff.

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 simple list tool with two optional pagination parameters and no output schema, the description covers the basic purpose but omits important behavioral context like pagination semantics and what fields are returned. It is minimally adequate for a straightforward resource, but not fully complete.

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?

The input schema fully documents both parameters (limit and offset) with descriptions including default and max values, so schema coverage is 100%. The description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 action (List) and resource (geo targets), with a clarifying parenthetical that defines what geo targets are. This distinguishes it from sibling tools like get_geo_target, create_geo_target, and other list_* target tools.

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 gives a clear listing purpose but offers no explicit guidance on when to use this tool versus alternatives such as get_geo_target for a single target or list_postal_code_targets for other targeting types. No exclusions or alternative recommendations are mentioned.

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