Find EV charging stations near a latitude and longitude using Open Charge Map, with adjustable search radius and result limits for trip planning or charging access checks.
Find EV charging stations near a location from Open Charge Map.
| Name | Required | Description | Default |
|---|---|---|---|
| distance | No | Search radius in km (default 10). | |
| latitude | Yes | Latitude. | |
| longitude | Yes | Longitude. | |
| max_results | No | Max stations (default 10, max 50). |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It implies a read-only search but does not disclose authentication needs, rate limits, result ordering, pagination, or what the response contains.
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 front-loaded sentence with no wasted words. It is appropriately sized for a simple search tool and gets straight to the purpose.
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?
The input schema fully covers the parameters, so inputs are clear. However, with no output schema, the description does not explain return values, pagination, or operational constraints, leaving meaningful gaps for an agent calling the tool.
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%, and the schema documents all four parameters including defaults and limits. The description only says the search is near a location and adds no extra parameter meaning beyond the schema, so the baseline 3 applies.
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 states a specific verb (Find), resource (EV charging stations), scope (near a location), and data source (Open Charge Map). An agent can identify exactly what this tool does without opening the 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?
It implies the tool is for nearby EV station searches but gives no when-to-use guidance, no when-not-to-use conditions, and no alternatives. The required latitude/longitude inputs are only conveyed through the schema, not the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.