Clear Apple Health Incremental Import Cache

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

Annotations indicate destructive, non-read-only, idempotent. Description adds behavioral context: clears a specific file, affects future list calls, and auto-invalidates on mtime change. No contradiction.

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?

Three focused sentences with no fluff. Front-loaded with the action, then conditional usage. Excellent efficiency.

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?

Covers the main behavior and usage context. Lacks explanation of the response_format parameter, but the tool is simple and the parameter is secondary. Adequate for a low-complexity tool with good annotations.

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 coverage is 0% and description does not address the single parameter (response_format). While the parameter is optional and has a default, the description misses an opportunity to explain its effect on output.

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?

Clear, specific verb+resource: 'clear the incremental import cache'. Distinguishes from siblings by mentioning its role in forcing a full re-parse, which is unique among the listed 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?

Explicitly states when to use ('when you want to force a full re-parse without changing the export file') and notes auto-invalidation context. Lacks explicit 'when not to use' or alternatives, but this is acceptable given the tool's specific niche.

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