whoop_lifeos_update

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

No annotations provided; description discloses backup creation before writing and dry_run behavior, but does not detail permissions, destructiveness, or whether updates are incremental or overwriting.

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 concise sentences in German, front-loaded with the main purpose, followed by constraints and dry_run behavior. 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?

For a simple tool with one parameter and an output schema (signal present), the description covers the key actions, constraints, and safety feature (backup), making it adequately 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?

With only one parameter (dry_run) and 0% schema coverage, the description effectively explains its purpose: 'Mit dry_run werden die Aenderungen nur angezeigt.' This adds value beyond 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?

The description clearly states the tool writes recovery, sleep, and strain into the Life-OS dashboard, distinguishing itself from sibling tools by specifying it only updates Whoop fields and leaves others untouched.

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 description mentions what the tool does not affect (Strava activities, weight, nutrition) and dry_run mode, but lacks explicit guidance on when to use this tool versus siblings 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.