get_stations_in_area

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

The description says 'Get' implying a read-only operation, but annotations indicate readOnlyHint=false and destructiveHint=true, suggesting potential side effects or data destruction. This is a direct contradiction, and the description fails to disclose any behavioral traits beyond the basic action.

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, concise sentence with no wasted words. However, it could be slightly more informative without losing conciseness, e.g., by noting the return type or limitations.

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 potential for destructive behavior (per annotations), the lack of explanation about side effects, return format, or operational limits makes the description incomplete. The minimal information does not compensate for the complexity implied by annotations.

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% for both parameters (bbox format and fuel type codes). The description adds no extra meaning beyond what the schema already provides, so a baseline score 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 'Get fuel stations within a bounding box' clearly states the verb (Get), resource (fuel stations), and scope (bounding box). It effectively differentiates from sibling tools like find_nearest_stations (point-based) and find_route_stations (route-based).

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 implies usage when a bounding box is available, but it does not explicitly state when to use this tool over alternatives like find_nearest_stations or calculate_route. No guidance on prerequisites or limitations is provided.

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