Find EV charging stations

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions key behaviors beyond the bare operation: results are sorted by distance, and filtering is optional. It is a read-only search tool, so there are no destructive side effects to disclose. However, it does not mention radius usage or return format, which are minor gaps.

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 sentence that front-loads the main action and resource, then appends filtering and sorting details. Every word contributes meaning; there is no redundancy or filler.

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?

For a simple read-only query tool with 5 parameters and no output schema, the description covers the primary operation, filtering options, and sort order. It does not explain the result structure, but the purpose is clear enough for an agent to invoke it correctly. The absence of output schema is partially mitigated by the description's clarity.

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%, so the baseline is 3. The description adds marginal value by phrasing 'optionally filtered by connector type and minimum charging power', reinforcing the optional nature of those parameters. It does not add new syntax or clarify units beyond what the schema already provides.

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 ('Locate') with a clearly scoped resource ('electric vehicle charging stations') and adds filtering and sorting criteria. This clearly distinguishes it from siblings like find_parking_facilities or find_nearby_places, which cover different resource types.

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 establishes clear context: it is for finding EV charging stations near a location, with optional filtering by connector type and power. It does not explicitly name alternatives or mention when not to use it, but the specificity of the resource makes the intended use unambiguous.

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