Bike station status

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered. The description adds the useful 'live'/real-time qualifier and lists what status fields are surfaced, but says nothing about what happens for an unknown station_id or about rate limits.

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 front-loaded sentence with the resource first and the returned fields after the colon. No filler, no repetition of the title.

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?

Since an output schema exists, the description needn't explain return values, and the live-status framing is enough on that front. However, for a 2-required-parameter tool with an entirely undocumented station_id, the definition leaves the agent guessing where that identifier comes from.

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 coverage is only 50%: network_id is documented inline (including its source tool), while station_id has no schema description whatsoever. The description does not mention any parameter and so fails to compensate for that gap, e.g. by explaining that station_id must come from nearby_stations or how it is formatted.

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 resource (one station) and enumerates the state it returns (bikes, e-bikes, free docks, rental/return capability), which clearly separates it from the list-style siblings search_networks and nearby_stations. It does not explicitly name those siblings, so it stops short of full disambiguation.

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?

"One station" implies the tool is for a known station id, which is useful implied guidance, but there is no explicit when-to-use vs. when-to-use-nearby_stations statement and no pointer to how a station_id should be obtained. Nothing actively misleading, just under-specified.

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