Philippine-Geocoding

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

No annotations are provided, so the description carries the full burden. It mentions 'List all cities' but doesn't disclose behavioral traits like whether this is a read-only operation (implied but not stated), potential rate limits, pagination needs, or what the output format looks like (e.g., list of names, objects with details). For a tool with zero annotation coverage, this is insufficient.

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, efficient sentence with zero waste. It's front-loaded with the core action ('List all cities') and specifies the scope ('in the Philippines'), making it easy to parse quickly.

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?

Given the complexity (a list operation with many sibling tools), no annotations, and no output schema, the description is incomplete. It doesn't explain what 'cities' means (e.g., including municipalities?), how results are returned, or any limitations (e.g., all cities at once vs. paginated). For a tool in a crowded namespace, more context is needed.

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 tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate as it doesn't miss anything. No points are deducted since there's nothing to compensate for.

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 verb ('List') and resource ('all cities in the Philippines'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_city' (singular) or 'get_region_cities', which might filter by region. This prevents a perfect score.

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 no guidance on when to use this tool versus alternatives like 'get_city' (for a specific city), 'get_region_cities' (for cities in a region), or 'search_by_name' (for searching). It simply states what it does without context about when it's appropriate.

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