list_stations

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

No annotations are provided, so the description carries the full burden, and it does disclose one genuinely behavioral fact: results are filtered by the invoking token's permissions. It says nothing about pagination, ordering, or the shape/volume of the response, which are the traits an agent would still need for a listing operation.

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?

A single short sentence with the scope qualifier front-loaded and no filler. Nothing could be trimmed without losing the access-scoping meaning.

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?

For a trivial zero-parameter read tool this is close to sufficient, but with no annotations and no output schema the description is the only source of information, and it omits any indication of what a station record looks like or how results are bounded.

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 tool takes zero parameters, so there is no parameter meaning for the description to add. Baseline 4 applies; the description introduces no param-related confusion.

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?

"List all stations accessible with the current token" pairs a specific verb (list) with a specific resource (stations) and adds a meaningful scope qualifier — only stations the token can reach. An agent can distinguish it from singular siblings like get_station and update_station by the plural, read-only framing. It stops short of naming those siblings explicitly.

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 phrase "all stations accessible with the current token" implies this is the discovery/enumeration entry point, which is useful context. However, it never states when to prefer this over get_station for a single station, nor whether it is the required first call before other station-scoped tools.

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