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

No annotations are provided, so the description must disclose behavioral traits. It adds the refresh interval ('Data refreshes every 10 minutes') which is a useful behavior. However, it does not explicitly state read-only semantics, error handling, or the exact return format. The listed fields provide some transparency, but the burden is only partially met.

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 a single, front-loaded sentence with no filler. It conveys the core purpose and key details (data fields and refresh rate) efficiently. Every word contributes value, making it highly concise and well-structured.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential information: purpose, data fields returned, and refresh behavior. It lacks an explicit return format or error conditions, but the field list provides sufficient context for an agent to invoke the tool correctly.

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 schema covers 100% of the parameter descriptions, with 'city' described as 'City id: one of manchester'. The tool description adds no additional parameter context, but since the schema provides complete documentation, the baseline of 3 is appropriate.

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 clearly states the tool's purpose: 'Live network totals for a city' and enumerates specific data fields (bikes available, e-bikes, active stations, bikes docked). This specific verb+resource combination distinguishes it from sibling tools like find_stations or get_availability_trend, which focus on station-level or trend data.

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 description provides clear context for when to use the tool: when you need city-level network totals. It implies usage by listing the data fields, but does not explicitly mention alternatives or exclusion scenarios. This meets the 'clear context, no exclusions' level, though it stops short of naming sibling tools as alternatives.

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