Clear Samsung Health Incremental Import Cache

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

Annotations already mark it destructive and idempotent, but the description adds context by specifying the exact file path, what the cache tracks, and the requirement for explicit user intent. It clarifies that this only affects local cache, not source data, going beyond the annotations.

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 four sentences, each serving a distinct purpose: action, background, usage, and gating. It is efficiently written and front-loads the primary action.

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 simple cache-clearing utility, the description fully explains the tool's behavior, use case, and caveats (auto-invalidation, explicit intent). No output schema is needed, and the parameter is trivial.

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 only parameter, response_format, is self-explanatory from the schema enum and default, but schema description coverage is 0% and the description does not mention it. For such a trivial parameter this is acceptable, but the description could have explicitly stated the default 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?

The description explicitly states the action (clear) and the specific resource (~/.samsung-health-mcp/incremental-cache.json), explaining the cache's role and differentiating it from simply deleting a file. The 'Use this when' clause further clarifies its specific purpose.

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?

It provides explicit guidance on when to use the tool: 'Use this when you want to force a full re-parse without changing the export file.' It also notes auto-invalidation on mtime change, which signals when manual clearing is unnecessary.

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