get_full_snapshot

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

No annotations are provided, so the description carries the full behavioral burden and fails it: nothing about which metrics are bundled, whether this is an expensive/aggregating call, caching, or any permission requirement. The only hint is 'comprehensive', which is not a behavioral trait an agent can act on.

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?

A single short sentence with no padding, front-loaded with the resource. It is efficient, though the brevity here reflects under-specification rather than tight writing.

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 explained, but for a tool whose entire value proposition is breadth, the description never says what data is aggregated or how the two windows interact with the result. Against a dense sibling set, this leaves the agent unable to judge when the snapshot is the right 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?

Schema description coverage is 100%, so both windows (load_days, activity_days) are fully documented with defaults and bounds in the schema. The description adds no syntax, format, or interaction detail beyond that, which is the expected baseline when the schema does the work.

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 resource ('Garmin data snapshot') and an implied retrieval action, but the verb is nominal and the scope is vague — 'comprehensive' and 'holistic' do not tell an agent what is actually inside the snapshot. It also never distinguishes itself from the many targeted siblings (get_fitness, get_recovery, get_training_load), so the agent cannot tell whether this duplicates or aggregates them.

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?

No when-to-use guidance at all. With 14 siblings covering individual metrics, the description should say to use this for a broad overview instead of several targeted calls — that routing information is entirely absent.

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