Fetch the newest exercise data from COROS APIs and rebuild the local catalog with human-readable names.
Fetch the latest exercise catalog from COROS APIs and rebuild the local catalog. Requires authentication. Fetches exercises from the COROS API and i18n strings for human-readable names.
| Name | Required | Description | Default |
|---|---|---|---|
| sportType | No | Sport type to fetch exercises for (default 4 = strength) |
Changes observed during successful MCP inspections.
v2.2.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that the tool mutates local state by rebuilding the local catalog and that authentication is required, which adds value beyond the annotations. It does not state whether the rebuild is incremental or destructive, whether existing exercises are removed, or what happens if the upstream API fails, leaving some important runtime behavior unspecified.
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 short and front-loads the primary action. The second sentence is somewhat redundant with the first, but it adds the useful i18n detail. Overall, it is efficient and readable.
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?
The tool is simple, with one optional parameter, and the description covers the data source, authentication, and the local rebuild effect. However, there is no output schema and no mention of return values, completion signals, or the impact on existing catalog entries, so an agent must guess what a successful invocation returns.
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 already documents the only parameter (sportType) with its default and meaning, reaching 100% coverage. The description adds no parameter-level guidance, so it remains at the schema-coverage baseline. No additional ambiguity is introduced, but the description also does not help the agent choose a non-default sportType.
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?
States a specific operation: fetching the latest exercise catalog from COROS APIs and rebuilding the local catalog. This is far more informative than the bare tool name and makes the tool's role clear. It does not explicitly name or distinguish from sibling tools like search_exercises, but the resource and action are unambiguous.
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?
Gives a clear use case (refresh/rebuild the exercise catalog) and an explicit prerequisite (authentication exists). However, it does not say when not to use this tool or when a sibling like search_exercises would be more appropriate. With a large sibling set, the missing routing guidance is a real gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.