get_top_voted_stations

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

With no annotations provided, the description must carry the behavioral burden. It implies a read-only GET operation and sorting by votes, but it does not disclose timeout behavior, count handling, or any other caveats. The description adds little beyond the endpoint itself.

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 extremely concise with no redundant wording, and the endpoint template adds practical value. However, it reads more like a title than a self-contained description, so it earns high but not full marks.

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?

While an output schema exists, the description lacks usage alternatives and behavioral context. An agent cannot determine when to choose this over similar list tools or what the timeout parameter means. For a two-parameter tool with no annotations, this is insufficient context.

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 0%, so the description should compensate. The 'count' parameter is partially inferable from the URL template, but 'timeout' is completely unexplained. Neither parameter gains meaningful semantic context beyond its name.

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 specifies the resource ('highest-voted stations') and the endpoint with GET, making the retrieval intent clear. It is distinguishable from siblings like get_most_clicked_stations or get_recently_updated_stations, though it lacks an explicit verb such as 'retrieve' or 'list'.

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?

There is no guidance on when to use this tool versus alternatives. Siblings like get_most_clicked_stations or get_recently_updated_stations are not contrasted, so the agent must infer usage purely from the phrase 'highest-voted'.

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