get_enhanced_detours

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

Discloses beyond the schema that it may return an 'Unsupported function' error due to a CTA-side limitation, explaining that this is not a tool bug. This is valuable behavioral context not covered by annotations (which are absent).

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 very concise: two sentences with no wasted words. It front-loads the main purpose and then adds a critical behavioral note.

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 no parameters and an existing output schema, the description covers the tool's purpose, output contents, and a potential error case. It is complete for its simplicity.

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?

No parameters exist in the input schema, so the description is not required to elaborate on parameters. The baseline score of 4 applies.

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 it fetches enhanced detour data including affected patterns, trips, and stops. It doesn't explicitly differentiate from the sibling tool 'get_detours', but the term 'enhanced' implies a distinction.

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?

Provides context for when to use (GTFS-RT systems needing detour data) and warns about a potential error scenario. However, it does not explicitly state when not to use it or mention alternatives like 'get_detours'.

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