nearby_stops

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

Without annotations, the description should disclose behavioral traits. It only states the basic function, omitting details like whether results are sorted by distance, what happens if no stops are found, or any performance implications. This leaves significant gaps for a tool that queries geographic data.

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 that efficiently conveys the core function. However, it could benefit from slight restructuring to include key parameter context without becoming verbose.

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 tool has 4 parameters, no output schema description, and the description does not address return values or edge cases, it is incomplete. The agent lacks information about the structure of the output or how to interpret the results, which is critical for a tool that returns a list of nearby stops.

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 0%, meaning no parameters are documented in the schema. The description adds no information about the four parameters (latitude, longitude, max_stops, max_radius_meters), such as their units, constraints, or how they affect results. The agent must rely solely on parameter names, which may be insufficient.

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 clearly states the verb 'Devuelve' (returns) and the resource 'paraderos de transporte público más cercanos' (nearest public transport stops), making the purpose unambiguous. It effectively distinguishes from sibling tools like get_stops (which lists stops generally) or get_routes_at_stop (which focuses on routes).

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?

No guidance is provided on when to use this tool versus alternatives such as get_stops or find_route. There is no mention of prerequisites, limitations, or typical scenarios, leaving the agent without decision-support information.

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