Find CityBus stops

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

No annotations are provided, so the description must carry full behavioral disclosure. It omits key details: whether query and lat/lon can be combined, what happens when both are provided, pagination behavior, and the absence of any mutability warnings. The description is too sparse for a tool with no annotations.

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 purpose and source are front-loaded, and the structure is optimal for quick scanning.

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 has 4 optional parameters, no output schema, and no annotations. The description fails to clarify return format, parameter interaction (e.g., can both query and lat/lon be used together?), or the meaning of 'nearest' (radius, ordering). While adequate for a simple tool, gaps remain that could confuse an agent.

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%, so baseline is 3. The description adds minimal value beyond parameter descriptions, only mapping 'by name' to query and 'nearest a lat/lon' to lat/lon. It does not clarify mutual exclusivity or default behavior, so it does not exceed the baseline.

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's two modes: searching by name or finding nearest stops by lat/lon. It specifies the source (CityBus GTFS) and implicitly distinguishes from sibling tools like bus_next_departures and bus_routes by focusing on stop location lookup.

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 implies use cases (search by name or find nearest stops) but does not explicitly contrast with sibling tools or provide when-to-use/when-not-to-use guidance. For a tool with 30+ siblings, more explicit direction would help selection.

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