Remove a workout from the feed by its ID so it is no longer scheduled; the watch clears it at the next sync.
Remove one workout from the feed by id; HoodaRun removes it from the Watch at its next sync.
| Name | Required | Description | Default |
|---|---|---|---|
| workout_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It does disclose one genuinely valuable trait — removal propagates to the Watch only at the next sync, not immediately — but omits whether the removal is reversible, what permissions are needed, and what happens for an unknown or already-unscheduled id.
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?
One sentence, two clauses, front-loaded with the action and selector, with the sync behavior as supporting detail. Nothing is redundant.
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?
For a one-parameter removal tool with no output schema and no annotations, the description covers the essential operational surprise (delayed Watch sync). Missing only id provenance and failure behavior, which are minor for this shape.
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 single parameter has no title or description beyond 'Workout Id'. The description only adds that the id selects the workout to remove; it does not say where the id comes from (e.g. list_scheduled) or its format.
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?
Specific verb (Remove) plus resource (one workout from the feed) and the selector (by id). The phrase 'one workout' implicitly separates it from the sibling clear_scheduled, which presumably clears the whole feed, but the differentiation is by implication rather than explicit contrast.
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?
Usage is only implied: 'Remove one workout' suggests single-item removal versus clear_scheduled's bulk clearing, but the description never names that alternative or states the condition for choosing it. No prerequisites or error cases (e.g. unknown id) are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.