Detalle del servicio de bus

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

No annotations provided, so description carries full burden. It discloses the return content (seat map, boarding points) but does not mention error handling, side effects, or data freshness. For a read operation, it is adequate but could be more forthcoming.

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: first explains purpose, second covers prerequisites. No redundant information, front-loaded with purpose. Every part earns its place.

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 7 parameters, 5 required, and no output schema, the description covers return structure (seat map fields, boarding points with times/addresses) and prerequisites. Could mention error scenarios or pagination, but overall complete enough for an action.

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 100% (baseline 3). The description adds value beyond schemas by explaining how to obtain IDs ('obtenido de 'buscar_buses') and constraints on 'fecha' (must be same as search, today or future). Defaults for 'max_asientos' and 'solo_disponibles' are also clarified.

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' and the resource 'detalle de un servicio de bus concreto', specifying that it returns seat map details and boarding/alighting points. This distinguishes it from sibling tools like 'buscar_buses' which is for searching 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?

Explicitly states prerequisites: 'Requiere routeId, operatorId y los IDs de ciudad que entrega 'buscar_buses'. This tells the agent when to use this tool (after searching buses) and implies it is not for initial search. No explicit when-not-to-use, but clear enough.

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