Philippine-Geocoding

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

No annotations are provided, so the description carries full burden. While 'Get all cities' implies a read-only operation, it doesn't disclose important behavioral traits like whether this returns a complete list or paginated results, what format the cities are returned in, whether there are rate limits, or what happens with invalid province codes. The description is minimal and lacks behavioral context.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads the core functionality.

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 no annotations, no output schema, and 0% schema description coverage, the description is incomplete. For a tool with many similar siblings in the server, it should provide more context about what distinguishes it, what format the results take, and any constraints or requirements. The current description leaves too many questions unanswered.

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 schema has 0% description coverage, so the description must compensate. It mentions 'specific province' which relates to the 'provinceCode' parameter, but doesn't explain what format the province code should be (string format, valid values, examples) or provide any additional semantic context beyond what's implied by the parameter name itself.

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 ('Get all cities') and target resource ('within a specific province'), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_cities' or 'get_province_cities_municipalities', which appear to have overlapping functionality.

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. With many sibling tools that appear related (like 'get_cities', 'get_province_cities_municipalities', 'get_region_cities'), there's no indication of when this specific tool is appropriate versus those other options.

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