stop_list_export_download

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

The description adds no behavioral context beyond the annotations. It does not disclose whether the download is one-time, what the response format is, or any side effects. The annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds nothing beyond that.

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 short and front-loaded with the endpoint, which is concise. However, it is not a proper explanatory description and lacks structure that would help an agent understand the tool's function.

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 is simple with only two parameters and complete schema/annotation coverage, but the description omits crucial context such as the need to obtain a token from stop_list_export_create first and what the returned payload represents. This makes the description incomplete for effective tool selection.

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% (both token and dry_run have descriptions), so the description does not need to add parameter details. The description text adds no extra meaning about the parameters; it simply repeats the endpoint.

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 is merely the endpoint 'GET /api/v2/stop-list/export/{token}' which essentially restates the tool name without explaining what the tool does. It lacks an explicit verb like 'downloads' or 'retrieves', and does not distinguish from siblings like api_get_v2_stop_list_export_token.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that a token must first be created via stop_list_export_create, nor does it exclude use cases. This is a clear gap for a tool with several related export operations.

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