Weekly report

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

Annotations declare readOnlyHint=true, so no destructive behavior. The description adds detail on output structure (per-day grid, weekly averages, workout totals) beyond annotations, but does not mention other behavioral aspects like pagination or rate limits, which are not needed given the simple read-only nature.

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 concise (two sentences plus a parameter note), front-loading the core purpose. Every sentence adds value with no redundancy.

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?

Given the tool's simplicity (one optional parameter, read-only, output schema exists), the description sufficiently covers what the tool does, its output content, and how to use the parameter. No gaps remain for the agent to make an informed call.

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 explicitly explains the 'week_of' parameter with acceptable formats ('this week', 'last week', 'YYYY-MM-DD'), adding essential meaning beyond the bare 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 it produces a 'Monday-to-Sunday report' with specific metrics (recovery, sleep, strain, weekly averages, workout totals), distinguishing it from siblings like get_daily_summary or get_sleep. The verb 'get' and resource 'weekly report' are well-defined.

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 provides clear parameter guidance ('week_of' accepts specific values), and the weekly nature implies use for weekly overviews. However, it does not explicitly state when to use this tool versus related siblings like get_recoveries or get_sleep_trends.

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