fitness_daily_brief

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, establishing safety and non-destructiveness. The description adds value by noting data aggregation from Apple with Garmin as fallback, and that output is a string. No contradictions with annotations.

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 extremely concise: two sentences plus an Args/Returns section. It is front-loaded with the core purpose and efficiently conveys all essential information without fluff.

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 moderate complexity as an aggregator, the description covers key aspects: data sources, components retrieved, and return format. It does not detail error handling or missing data scenarios, but these are minor gaps. Overall sufficiently complete for a read-only summary tool.

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 description does not mention parameters, but the input schema provides clear descriptions for both 'date' (format and default) and 'response_format' (enum with defaults). With schema covering parameter semantics adequately, a baseline of 3 is appropriate despite zero description coverage.

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 provides a morning brief summarizing recovery (HRV, sleep, resting HR from Apple with Garmin backup), yesterday's training, and today's planned workouts. It distinguishes itself from individual Garmin data tools and other composite summaries, making the purpose unmistakable.

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 using this tool for a consolidated morning brief instead of calling multiple individual tools. However, it lacks explicit when-to-use or when-not-to-use guidance, and does not name alternatives directly. Context is clear but not fully prescriptive.

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