whoop_invalidate_cache

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

With no annotations provided, the description carries the full burden of disclosing behavioral implications. It states the tool invalidates cache, but omits side effects (e.g., whether it clears all cache, affects other requests, or requires authentication). No details on reversibility or performance impact are given.

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 a single, well-front-loaded sentence that communicates the primary action and its effect without unnecessary words. It earns its place and is appropriately sized for a simple tool.

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 zero-parameter, no-output-schema tool, the description covers the core action but lacks contextual completeness. It does not explain when this action is needed, what happens after invalidation, or how it interacts with caching behavior. While adequate for a simple operation, a short note on usage context would improve it.

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 tool has zero parameters, so the baseline is 4. The description correctly focuses on the operation rather than parameters, and there is no schema coverage issue since no parameters exist. Nothing is omitted that could disambiguate input expectations.

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 'Force fresh data on next request by invalidating the cache' clearly states the tool's function with a specific verb ('invalidating') and resource ('the cache'). It distinguishes itself from sibling getter tools by being the only cache-management operation.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description implies a scenario (stale data) but does not state exclusions, prerequisites, or contrast with getters or cache status checks. The sibling tool 'whoop_get_cache_status' might be relevant but is never mentioned.

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