Get station

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful note that tracks/users carry a station_urn (an entity relationship) but says nothing about pagination of the tracks or what the response looks like. Adequate value beyond annotations, not rich.

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?

Two compact sentences, front-loaded with the core action, then a cross-reference hint. No redundant or filler wording.

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?

A simple two-parameter read tool with a fully described schema and readOnly annotation; the description covers purpose, entity relationships, and a discovery path. It stops short of explaining track pagination or the compact-vs-verbose result shape, but there is no output schema and the gaps are small.

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%, with both stationUrn and verbose fully documented in the schema (including URN formats). The description adds no parameter-level detail beyond restating the object type, so the baseline 3 for high coverage is correct.

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?

States a specific verb+resource and disambiguates it: 'Get a station (system playlist) and its tracks'. The parenthetical clarifies that a station is a kind of system playlist, which distinguishes it from get_playlist and get_playlist_tracks among siblings. An agent can tell what it retrieves without opening the schema.

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?

Implies when to use it (when you have a station_urn and want the station plus its tracks) and points to get_my_likes with kind=stations for discovering liked stations. However, it never explicitly says when to use get_station versus get_playlist/get_playlist_tracks, so the boundary with close siblings is left implicit.

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