Look up a US city or town by name (free, no key). Returns matches with their census place GEOID and centre point (lon/lat). The entry point: feed a GEOID to blocks_in_area, or a centre to walkability_summary.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max matches (1-20). | |
| query | Yes | City or town name, e.g. 'Providence'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses that the tool is 'free, no key' and returns specific data (GEOID, centre point). This is sufficient for a read-only lookup tool. It lacks explicit mention of side effects, but none are expected.
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 exactly two sentences, both essential. The first states purpose and returns, the second provides usage chaining. No unnecessary 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?
Given the tool's simplicity (2 parameters, no output schema), the description is complete. It explains the return value and how to use it with sibling tools.
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 100%, with both parameters described. The description adds minimal extra meaning beyond the schema, such as 'City or town name' which is already in the schema. Baseline of 3 is appropriate.
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 uses specific verbs and resources: 'Look up a US city or town by name' and 'Returns matches with their census place GEOID and centre point (lon/lat).' It clearly distinguishes this tool from siblings like blocks_in_area and walkability_summary by stating it provides the input for them.
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 explicitly guides on how to use the output: 'feed a GEOID to blocks_in_area, or a centre to walkability_summary.' This provides clear usage context. However, it does not explicitly state when not to use this tool or suggest alternatives, but the purpose is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: blocks_in_area provides per-block travel times, isochrone gives reachable areas, nearby_pois gives times to specific POIs, walkability_summary gives times to destination categories, and the rest handle place lookup, catalog, tokens, and authentication. No two tools overlap in functionality.
Tool names mix styles: some start with verbs (find_place, get_catalog, redeem_code, request_sign_in), others are noun phrases (blocks_in_area, isochrone, nearby_pois, walkability_summary). There is no consistent verb_noun or noun pattern, making it harder for an agent to predict tool names.
With 10 tools, the server covers core travel time analysis, place lookup, authentication, and membership. The count is well-scoped for the domain—neither too few to be useful nor too many to be confusing.
The tool surface covers the major workflows: finding places, getting base data, computing travel times in various forms (blocks, isochrones, POIs, summaries), and managing API keys. Minor gaps exist (e.g., no direct tool for single-point travel time to arbitrary coordinates), but the set is largely complete for the stated purpose.
