List the current app user's cardio activities (most recent first).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| date_to | No | ||
| date_from | No |
| Name | Required | Description | Default |
|---|---|---|---|
| items | No |
Changes observed during successful MCP inspections.
Output schema / propertiesAdded value: +{
+ "items": {
+ "type": "array"
+ }
+}Output schema / (root)Previous value: -nullNew value: +{
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly and idempotent hints, and the description adds the sorting behavior and user scope. However, it does not disclose behavior about date filtering or pagination beyond what the schema implies.
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?
A single concise sentence with no filler, front-loading the action and resource.
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 description covers the core return (cardio activities) and ordering, and an output schema exists. However, it lacks guidance on the optional parameters and does not address filtering or limit behavior, making it incomplete for a tool with 3 undocumented params.
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 0% and the description does not mention any of the three parameters (limit, date_to, date_from). The parameter names are self-explanatory but the description provides no additional semantic value for them.
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 uses the specific verb 'List' and identifies the resource 'cardio activities' scoped to the current app user, with an ordering qualifier 'most recent first'. This clearly distinguishes it from sibling tools like get_workouts or get_meals.
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 implies usage when the user needs their cardio activity list, but it does not explicitly state when to use this tool versus alternatives like get_workouts or get_events. There are no exclusions or alternative recommendations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.