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

Annotations already assert readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes further by characterizing the response content and ordering ('the top 3 public rides... biggest first') and noting records are public-only, which is genuine behavioral context beyond the annotations.

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 payload is front-loaded in a single dense sentence, followed by a short clause explaining the parameter. It is appropriately sized for the amount of information conveyed, though the long enumeration makes it slightly heavy for a one-sentence structure.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them well. Combined with a fully documented single parameter and clear annotations, an agent has everything needed to call this correctly; only the missing explicit sibling routing keeps it from a 5.

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% and the single `venue` parameter is fully documented in the schema as a name or id. The description restates that but adds concrete example names ('bradley', 'snow summit'), a marginal gain over the schema — baseline 3 applies.

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 states a specific verb+resource (get one bike park) and enumerates the exact payload: runs and features with clip counts, clip/ride totals, records, newest clips. This is clearly distinguishable from siblings like list_venues and get_clip without opening any 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?

Usage is implied by the scope ('Everything about one bike park in one call'), but there is no explicit when-to-use or when-not-to-use guidance, nor any routing to list_venues (to discover a venue) or get_clip (for a single clip). The agent must infer the boundary from the sibling names.

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