Buscar buses

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

No annotations are provided, so the description carries the full burden. It discloses the tool's return values (company, bus type, schedules, prices, etc.) and that it is a read-only search operation. It does not mention rate limits or authentication, but for a simple search tool, the transparency is adequate.

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?

Two sentences with no wasted words. The first sentence states the core purpose, and the second provides a concise list of return values and usage guidance. Well-structured and efficient.

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 5 parameters, no output schema, and the tool's complexity, the description is complete: it covers the action, parameters, return values, and how to chain with detalle_servicio. No missing context for correct invocation.

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 80%, so the schema already documents most parameters. The description adds extra meaning by explaining that origen/destino accept names or IDs, and by detailing the output fields, including how to use results with detalle_servicio. This adds value beyond the schema.

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?

Description clearly specifies it searches for interprovincial buses in Peru via RedBus for a given route and date. It distinguishes itself from sibling tools (buscar_ciudades for city search, detalle_servicio for details) by explicitly mentioning that the results contain routeId/operatorId for use with detalle_servicio.

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?

Description indicates when to use (for route and date) and provides a usage hint about using detalle_servicio for more details. However, it does not explicitly state when not to use or mention alternatives beyond the implied sibling relationship.

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