get_body_composition

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and the sentence '(Garmin Connect, read-only...)' merely restates the safety profile. The word 'available' usefully hints that results may be sparse or partially missing, but nothing is said about permissions, date-span limits, or error behavior.

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?

Short and front-loaded, with the resource named first and the range constraint second. The parenthetical repeats the date format already stated in the main sentence, which is mild waste but not harmful.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What is missing for a 2-parameter read tool is any differentiation from sibling body/weight/metric tools and any note on enddate being optional, which the description should carry.

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?

Schema description coverage is 0%, so the description is the only source of semantics, and it does supply the YYYY-MM-DD format for both parameters. It does not explain that enddate is optional (schema default null) or what the behavior is when enddate is omitted, leaving a real gap.

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?

States a specific verb and resource ('Return available body composition data') scoped to a date range, so the agent knows exactly what is fetched. It does not, however, distinguish itself from overlapping siblings such as get_weigh_ins or get_stats_and_body, which plausibly return related body metrics.

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 gives no when-to-use condition beyond the date range format, and no exclusions. With several near-neighbour tools (get_weigh_ins, get_stats_and_body, get_user_summary) in the sibling list, the absence of any routing guidance leaves selection to inference.

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