Route schedules

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

The description discloses that the output is heavier, which is a behavioral characteristic. However, since no annotations are provided, it lacks explicit statements about side effects or errors, but for a read-only query tool this 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?

The description is concise, two sentences, with useful parenthetical notes. Parameter descriptions are also succinct and informative.

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 description covers its purpose, usage relative to alternatives, and output size. It doesn't include an example or output format, but that is not essential for such a simple query tool, so it's reasonably 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?

All parameters are described in the schema, and the description adds extra context such as how to find the id and that items_per_schedule defaults to 5 to keep output small, going beyond basic 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?

The description clearly states the tool provides a full timetable grid for a line or route, distinguishing it from stop_schedules and terminus_schedules. The verb is implicit but the purpose is unambiguous.

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?

It explicitly instructs to prefer stop_schedules for single-stop queries, providing clear when-to-use guidance relative to sibling tools.

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