rta_gtfs_static_url

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

Beyond the readOnly/idempotent annotations, the description discloses the credential model (anonymous 7z download, OAuth only for the query API), a dead alternate source (Transitland mirror returning 401 with 2021-era data), and the absence of any real-time feed. These are actionable facts an agent cannot infer from the schema or 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 purpose is front-loaded and each following sentence carries a distinct fact (auth model, dead mirror, no RT feed). It is slightly longer than the minimum but nothing is filler.

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?

With an output schema present and no parameters, the description need not explain return values or inputs. It covers the access/auth situation, a deprecated alternative, and feed scope, leaving no obvious question for the caller.

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?

There are zero parameters, so the baseline is 4 and there is nothing parameter-wise for the description to add or omit. No syntax detail is required.

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 first sentence gives a specific verb and resource ('Return download details for the RTA GTFS static feed'), which is unambiguous. It does not explicitly name a sibling or contrast itself with the rta_* tools, so it stops short of a 5, but the resource is distinctive enough that an agent can place it.

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?

Usage is implied by the resource name rather than stated. There is no explicit 'use this when...' and no named alternative tool, though the note that no GTFS-RT feed exists faintly bounds the use case. Adequate but with a clear gap.

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