stl_gtfs_stops

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is clear. The description adds search criteria but does not explain return format (e.g., returns a list) or pagination behavior via limit/offset, though this is less critical given the 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?

The description is a single, tightly worded sentence that conveys the core purpose without redundancy. It is well-structured and easily parsed by an agent.

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 is adequate for a simple search tool but lacks explanation of the 'snapshot' parameter (likely to select a data version) and does not describe the output schema. Given the tool's straightforward nature and presence of annotations, this is acceptable but not fully complete.

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 description explains three of six parameters: search (as case-insensitive substring), code (as exact match), and route_id (as serving route). It omits limit, offset, and snapshot, which are likely used for pagination and data versioning. This covers about 50% of parameters, providing basic but incomplete semantics.

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 'Search' and the resource 'stops', and enumerates specific search criteria (name substring, stop code, route). It distinguishes itself from sibling tools like stl_gtfs_stop (exact stop retrieval) and stl_gtfs_stop_resolve (ID resolution) by focusing on search functionality.

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 the many sibling tools. It does not mention that stl_gtfs_stop is for single-stop lookup or that stl_gtfs_stop_resolve handles fuzzy matching, leaving the agent to infer the appropriate context.

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