Find nearby Costco warehouse location records by latitude and longitude, ordered by distance. Use costco_search for product discovery rather than store locations.
| Name | Required | Description | Default |
|---|---|---|---|
| latitude | Yes | Latitude | |
| longitude | Yes | Longitude |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Input schema / properties / latitude / descriptionAdded value: +"Latitude"Input schema / properties / longitude / descriptionAdded value: +"Longitude"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one useful behavioral fact, that results are ordered by distance, but says nothing about result limits, radius bounds, or how 'nearby' is defined.
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?
Two sentences, zero waste, with the core behavior (what is found, how, and in what order) front-loaded before the sibling routing note.
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?
An output schema exists, so return values need not be described, and the description covers purpose, inputs, and the relevant alternative. It is slightly thin on proximity semantics (radius/limit) for a geo tool, but nothing essential 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 coverage is 100% but the property descriptions are merely 'Latitude' and 'Longitude', and the description adds no format, range, or unit guidance beyond restating that both are used. Baseline 3 is appropriate when the schema technically documents every parameter.
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?
States a specific verb (Find), resource (nearby Costco warehouse location records), the input basis (latitude/longitude) and the ordering (by distance). It also names the sibling it is not, so an agent can separate it from costco_search without opening either schema.
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?
Explicitly routes the agent to costco_search for product discovery as opposed to store locations, giving a clear condition for choosing the alternative. It does not enumerate any other exclusions or prerequisites, so it falls short of full when/when-not coverage.
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.