FirstCycling MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool returns (formatted string with team history, ranking positions, timeline, current status) but lacks details on error handling, rate limits, authentication needs, or data freshness. It adequately covers the output format but misses operational constraints.

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 well-structured with a clear purpose statement, usage note, examples, and return format. It's slightly verbose but each section adds value. The front-loaded purpose is effective, though the 'Returns' section could be more concise.

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 no annotations, 1 parameter with 0% schema coverage, and no output schema, the description does a good job covering purpose, usage, parameter meaning, and output format. It lacks details on errors or constraints, but for a read-only lookup tool, it provides sufficient context for basic use.

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 input schema has 0% description coverage, but the description compensates by explaining the parameter's meaning: 'rider's ID' is required, and examples show it's a numeric identifier (e.g., 16973 for Tadej Pogačar). This adds crucial context beyond the bare schema, though it doesn't detail ID format or sourcing beyond the search_rider reference.

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 with specific verbs ('get information', 'retrieves', 'provides') and resources ('professional cyclist's team affiliations and UCI rankings', 'team history', 'ranking points over time'). It distinguishes from siblings like get_rider_info or get_rider_teams by emphasizing the combined career progression focus.

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 explicitly provides when-to-use guidance: 'If you don't know the rider's ID, use the search_rider tool first to find it by name.' It names the alternative tool (search_rider) and specifies the prerequisite condition, offering clear operational context.

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