get_live_buses_on_route

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get real-time bus locations' without mentioning rate limits, data freshness, access requirements, or the read-only nature. The description fails to add meaningful behavioral context 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 extremely concise: a clear first sentence followed by two parameter explanations. No unnecessary words or repetition. It is front-loaded with the purpose and then lists parameters efficiently.

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 tool is simple with only two parameters and an output schema, so the description covers the basics. However, it could be more complete by mentioning that results are real-time (so may change rapidly) or what the output contains (e.g., bus IDs, locations). The sibling tools suggest more specialized queries, but the description does not help the agent decide when this is the best 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?

The input schema has 0% description coverage, but the description adds value by explaining operator_ref as 'Operator NOC code' with examples (ARBB, SCCM, CBBH) and line_ref as 'Route number' with examples (12, MK1, 100). This provides clarity that the schema lacks.

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 tool retrieves real-time bus locations for a specific operator and route. The verb 'Get' and resource 'real-time bus locations' are specific, and it distinguishes from siblings like 'find_buses_by_arrival_time' or 'plan_journey' by focusing on live data by operator and route.

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 provides no guidance on when to use this tool versus alternatives, such as when to use 'find_buses_by_arrival_time' or 'plan_journey'. There is no mention of context, prerequisites, or exclusions, leaving the agent without decision support.

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