Remove weight entries recorded on a specific date in Garmin Connect, with the option to delete all measurements for that day.
Delete weight measurements for a specific date
Args: date: Date in YYYY-MM-DD format delete_all: Whether to delete all measurements for the day
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | ||
| delete_all | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | 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 burden. It states the destructive action, but does not disclose whether deletion is permanent, what happens if delete_all is false, or any return/error behavior.
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?
Short, direct, front-loaded with the action and argument list; no unnecessary words.
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 lacks output description and leaves delete_all false ambiguous; for a destructive operation, more context is needed to be complete.
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?
It adds date format and describes delete_all as controlling whether all measurements for the day are deleted. It does not explain the false behavior or default, and there are no property-level descriptions in the schema.
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?
Clearly identifies the action (delete), the target (weight measurements), and the scope (specific date). It is distinct from sibling add/get weigh-in tools.
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 purpose statement implies the use case: call this when deleting weight measurements for a date. It does not explicitly mention alternatives or 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.