get_bus_locations

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It confirms the tool returns real-time data and accepts coordinates or stop identifiers, but omits details on permissions, rate limits, error handling, or what happens when no buses are found.

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 two sentences long, front-loaded with the core functionality, and each sentence adds distinct value. No unnecessary words or repetition.

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?

Despite moderate complexity (5 parameters, no output schema, no annotations), the description is too brief. It does not explain the output format, potential empty results, or how this tool relates to sibling tools like get_arrivals or nearby_stops. Critical operational details are 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?

The description adds meaning to parameters by mentioning 'coordenadas de referencia' (target_latitude/target_longitude) and 'paradero (stop_code, stop_id)', linking them to the tool's input. However, it does not fully specify how these parameters interact or constraints on combination. Given 0% schema coverage, this partial compensation is adequate but not thorough.

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 that the tool returns real-time GPS locations of buses in operation, with a specific route code example ('B10'). This uniquely identifies its purpose among sibling tools like get_arrivals (arrival times) and get_stops (stop lists).

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites, exclusions, or scenarios where it should not be used. It only lists capabilities without contextual comparison.

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