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. It discloses that the tool returns 'comprehensive information' and lists specific data points (e.g., team, nationality, recent results), which helps set expectations. However, it lacks details on potential limitations (e.g., data freshness, error handling, or rate limits), leaving behavioral gaps for a tool with no annotation support.

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 and front-loaded, starting with the core purpose. It uses bullet points for returns and examples efficiently, but includes some redundancy (e.g., repeating 'basic info' in examples when the description already states 'comprehensive information'). Overall, most sentences add value without excessive verbosity.

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, no output schema, and low schema coverage, the description does a good job by detailing the return format (formatted string with specific data points) and providing usage examples. It covers key aspects like purpose, parameters, and outputs, though it could improve by addressing potential errors or data scope limitations for better completeness.

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 (only 'rider_id' with type integer), so the description must compensate. It adds meaning by explaining that rider_id is required and provides examples (e.g., Tadej Pogačar ID: 16973), clarifying the parameter's purpose. However, it doesn't specify format constraints or sourcing details beyond the examples.

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: 'Get comprehensive information about a professional cyclist' with specific details like current team, nationality, date of birth, and recent race results. It distinguishes itself from siblings by focusing on a comprehensive overview rather than specialized queries (e.g., get_rider_victories or get_rider_race_history).

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 explicit guidance: 'If you don't know the rider's ID, use the search_rider tool first to find it by name.' This clearly indicates when to use this tool (with a known ID) versus an alternative (search_rider for unknown IDs), addressing a key usage scenario.

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