get_workouts

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

No annotations are provided, so the description carries full burden. It discloses ordering, time range, and source-specific data. However, it omits details like data freshness, authentication needs, rate limits, or behavior for invalid days values.

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 two sentences, front-loaded with the main action and key details. No unnecessary words or redundancy. It efficiently conveys purpose, scope, ordering, and data sources.

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 has one optional parameter and an output schema, so the description need not explain return values. It covers purpose, scope, ordering, and source specifics. Minor lack: whether there is a maximum `days` value or behavior for 0 days.

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 schema has 0% description coverage, but the description explains the `days` parameter (range, default 7, meaning 'last N days'). This adds value beyond the schema's type and default. No other parameters exist, so this is sufficient.

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 that the tool returns workout records from the last `days` days, ordered newest first, from two sources (WHOOP and Apple Health), with specific data included from each. This distinguishes it from sibling tools like get_daily_metric or get_sleep.

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 implies usage for retrieving recent workouts but does not explicitly state when to use this tool versus alternatives like health_context or get_recovery. No when-not-to-use or prerequisite information is provided.

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