resolve_placeResolve a place ID from search_places to an exact name, address, and coordinates.
| Name | Required | Description | Default |
|---|---|---|---|
| placeId | Yes | Place ID returned by search_places |
| Name | Required | Description | Default |
|---|---|---|---|
| place | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the resolution output contents but does not disclose error handling or behavior for invalid IDs; this is minor given the concise scope and strong annotations.
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?
A single sentence that front-loads the action and input, then immediately states the output fields. There is no filler, redundancy, or unnecessary detail.
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?
With only one parameter, an output schema available, and annotations covering side effects, the description fully covers the input origin, purpose, and output shape. Nothing an agent needs to call it correctly is missing.
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 description coverage is 100%: the placeId property is already documented as 'Place ID returned by search_places'. The description repeats this origin without adding additional parameter semantics beyond the schema.
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 a specific verb ('Resolve') with a clear resource ('place ID from search_places') and enumerates the output (exact name, address, coordinates). It clearly differentiates this from sibling tools like search_places, which finds candidates, and trip-planning 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 phrase 'from search_places' explicitly establishes the input source and implies the intended workflow: call search_places first, then resolve a selected ID. It does not explicitly state when not to use it or name alternatives, but the contextual chain is clear.
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 targets a distinct action: searching places, resolving a place, comparing ride-hailing, planning trotro-only trips, and comparing all modes together. Even where plan_trip overlaps with the mode-specific planners, the descriptions clearly position it as the multimodal default.
All tool names follow a consistent verb_noun snake_case pattern: compare_rides, plan_trip, plan_trotro_route, resolve_place, search_places. The naming is predictable and makes the purpose of each tool immediately clear.
Five tools is a well-scoped set for a ride-hailing and public transport comparison server. Each tool covers a necessary step in the workflow without redundancy or bloat.
The tool surface covers the full journey from place search and resolution through mode-specific and multimodal trip planning. There are no obvious dead ends or missing operations for the server's stated purpose of comparing and planning trips.