get_route_stops

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

With no annotations, the description carries the full behavioral disclosure burden. It only states what the tool retrieves; it does not mention read-only safety, response format, error behavior, direction handling, or any other runtime behavior. This is a noticeable gap for an unannotated tool.

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?

One clean, front-loaded sentence with no filler. Every word contributes to the purpose, and the description is appropriately sized for this simple tool.

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 description plus full schema coverage gives enough to attempt a call, but with no output schema and no annotations, details like return shape, ordering, and city/route constraints are missing. It is adequate but not complete for an agent operating independently.

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 description coverage is 100%, so the schema already documents city, route_id, and direction. The description adds minimal semantic context beyond mentioning 'route', which is already in the schema. Baseline 3 is appropriate.

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 names a specific action ('Retrieves stops and stations') and a specific resource ('transit route'), and it distinguishes itself from sibling tools like get_departures and get_service_alerts. An agent can clearly tell this is the route-stops lookup tool.

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 when stop/station information for a route is needed, but it gives no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. The usage context is inferable but not stated.

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