Server Quality Checklist

Tool Scores

• get_athlete_statsA
  3.5/5.0
  Behavior2/5

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

  With no annotations, the description carries the full burden for behavioral disclosure. It only lists returned data and does not mention auth requirements, rate limits, error handling, or return format, leaving significant behavioral traits undisclosed.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The two-sentence description is efficient and front-loaded, with no filler. Every sentence adds specific information about data categories and time periods.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The description covers the main data aspects but omits units, output structure, definition of 'recent,' and error behavior. Without an output schema or annotations, these gaps make it minimally complete but not thorough.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The single parameter athlete_id is fully described in the schema, including the hint to obtain it from get_athlete_profile. The description adds no extra parameter semantics, so the baseline of 3 applies.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool returns athlete statistics with specific metrics (distance, time, elevation) across three sports and three time ranges. This distinguishes it from siblings like get_athlete_profile (profile info) and list_activities (activity list).

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Usage is implied: the tool is for aggregate athlete stats, but the description does not explicitly state when to choose this over alternatives or any exclusions. It lacks direct guidance on when not to use it.

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

• list_routesA
  3.5/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries the full burden. It briefly mentions the return fields (name, distance, elevation gain, type) but does not disclose pagination, read-only nature, or ordering. This is a significant gap for a list operation.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single sentence that is front-loaded with purpose and contains no redundancy. Every word earns its place.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple list operation with no output schema and no annotations, the description provides basic return-field information but omits pagination and ordering behavior. It is minimally adequate but leaves clear gaps.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so the baseline is 3. The description adds no extra parameter semantics; it relies entirely on the schema's already-detailed parameter descriptions.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  Description clearly states the verb 'List' and resource 'saved routes', distinguishing it from siblings like get_route (specific route) and list_activities (activities). This is specific and unambiguous.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No explicit when-to-use or alternative guidance is given in the description. The only hint ('Get this from get_athlete_profile first') appears in the schema, not the description, so usage is merely implied rather than clearly contrasted with alternatives.

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

• get_activityA
  3.7/5.0
  Behavior3/5

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

  With no annotations, the description carries the burden. It states what data is included ('splits, segment efforts, and all metrics'), but does not disclose that include_all_efforts defaults to false, meaning segment efforts may be limited unless explicitly requested. It also does not mention any permissions or rate limits, though for a read operation this is less critical.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences, front-loaded with the purpose, and contains no fluff. Every sentence adds value: one explains the tool's function, the other clarifies a prerequisite step.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple read operation, the description is adequate but leaves ambiguity regarding how it relates to sibling tools like get_activity_laps and get_activity_zones. It does not clarify whether this tool returns laps/zones data or if those siblings are for specialized access. Given the presence of these siblings, more context would be helpful.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100% for both parameters. The description adds minimal value beyond the schema, only indicating that activity_id comes from list_activities. It does not explain include_all_efforts behavior beyond what the schema already contains, so baseline 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the verb and resource: 'Get detailed information about a specific activity'. It lists content (splits, segment efforts, metrics) and provides a prerequisite workflow ('Use list_activities first'). However, it does not explicitly distinguish from sibling tools like get_activity_laps or get_activity_zones, which could overlap in scope.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description gives clear context by instructing to use list_activities first to find IDs. However, it does not mention when to choose this tool over get_activity_laps or get_activity_zones, nor any exclusions. Thus it has clear context but no explicit alternatives.

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

• get_activity_lapsA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description carries the burden of behavioral disclosure. It states the output metrics (time, distance, pace, heart rate), which is useful, but it does not clarify whether the response is a single lap or an array, nor any access requirements or limitations. It only implies safety via the verb "Get".

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two concise sentences with the main action front-loaded. Every word contributes value with no unnecessary detail.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the low complexity (one parameter, no output schema), the description sufficiently explains what the tool does and what metrics are included. A minor gap is the lack of explicit statement about the return shape (e.g., array of laps), but it does not impede understanding for a simple read operation.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100% with activity_id described as "The activity's numeric ID." The description adds "for a specific activity" but provides no additional meaning beyond what the schema already documents.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  "Get lap data" is a specific verb+resource, and "for a specific activity" scopes it clearly. This distinguishes it from siblings like get_activity (overall activity) and get_activity_zones (heart rate zones), which serve different purposes.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies when to use the tool—when lap data is needed for a specific activity—but does not explicitly mention alternatives or exclusion criteria. It doesn't state that get_activity would be used for overall activity details, leaving the agent to infer the distinction.

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

• list_activitiesA
  3.8/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the transparency burden. It discloses pagination and return fields, and implies authentication via 'authenticated athlete'. However, it does not mention default ordering, rate limits, or error behavior, which are relevant for a list endpoint.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two concise sentences, front-loaded with the main action and followed by return summary. Every word contributes value, with no redundancy or filler.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Despite having no output schema, the description specifies the returned fields (name, type, distance, time, elevation) and mentions pagination. It does not explain default ordering or pagination defaults, but these are minor for a simple list tool. Overall, it provides sufficient context for the tool's basic use.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema has 100% coverage with descriptions for all four parameters (page, after, before, per_page). The description adds no parameter-specific details beyond the general mention of pagination, so it meets the baseline but does not exceed it.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool lists recent activities for the authenticated athlete, using a specific verb and resource. It distinguishes from sibling get_activity by focusing on listing multiple activities with summary data rather than a single activity.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage for listing activities but does not explicitly state when to use this tool versus alternatives such as get_activity or get_activity_stats. No exclusions or when-not-to-use guidance is provided, so guidance is implicit rather than explicit.

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

• get_activity_zonesA
  4/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the full burden. It uses read-only verbs ('Get', 'Shows') implying a safe read operation, but does not disclose any additional behavioral aspects such as return format, pagination, or potential errors. This is adequate for a simple read tool but lacks deeper transparency.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is extremely concise, two sentences, front-loaded with the main action, and contains no redundant information. Every word earns its place.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool has only one parameter, no output schema, and a straightforward read operation, the description is largely complete. It explains what is returned (time per zone) and is well differentiated from siblings. A slight gap is the lack of mention of response structure, but this is not critical for a simple tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema already fully describes the only parameter (activity_id) with 100% coverage. The description adds minimal extra context by referencing 'a specific activity', which aligns with the schema. The baseline of 3 is appropriate since the schema handles parameter semantics.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool retrieves heart rate and power zone distribution for a specific activity, using the verb 'Get' and naming the exact resource. It distinguishes itself from sibling tools like get_activity and get_activity_laps by focusing specifically on zone distribution.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  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 a user needs heart rate and power zone distribution for a specific activity. It does not explicitly mention alternatives or when not to use it, but the context is specific enough for an agent to select it appropriately among siblings.

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

• get_routeA
  4/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the full burden. It discloses the return content (distance, elevation, waypoints) but does not mention read-only status, error handling, required permissions, or response format. 'Get' implies a safe read, but behavioral depth is limited.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single sentence that is front-loaded and contains no filler. Every word adds value, specifying both the action and the key output components.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a tool with one parameter and no output schema, the description adequately conveys what the tool returns and its scope. It could be improved by noting that it's a read-only operation or when NOT to use it, but the core functionality is clear.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema already fully describes route_id as a numeric ID with 100% coverage. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline 3 applies.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states it retrieves detailed information about a specific route, listing example content (distance, elevation profile, waypoints). This distinguishes it from sibling tools like list_routes, which lists routes, and get_activity, which targets activities.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The context is clear: use when you need detailed information for a single route given its ID. It doesn't explicitly name alternatives or exclusions, but the phrasing 'specific route' versus list_routes implies selection of one route rather than listing all.

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

• get_athlete_profileA
  4.2/5.0
  Behavior3/5

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

  With no annotations provided, the description must carry the full burden of behavioral disclosure. It implies a read-only operation via 'Get' and specifies content, but doesn't explicitly mention authentication requirements, potential errors, or absence of side effects. This is adequate for a simple getter but lacks depth.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single sentence of 10 words, front-loaded with the verb and resource, and every word contributes meaning. It is efficiently concise.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's simplicity (no parameters, no output schema), the description provides the essential context: the resource and its key fields. It could explicitly mention the return format or authentication context, but it is reasonably complete for a profile retrieval tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The tool has zero parameters, so the schema covers everything (100% coverage). The description adds context about what the profile includes, but since there are no parameters to explain, the baseline of 4 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's function with a specific verb ('Get') and resource ('authenticated athlete's profile'), and lists contents (name, location, preferences). This distinguishes it from siblings like get_athlete_stats, which focuses on statistics.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description gives clear context about when to use this tool (retrieving the current athlete's profile) without explicit alternatives or exclusions. The differentiation from get_athlete_stats is implied by the resource type, providing adequate guidance.

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