garmin_profile

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that settings are Garmin's 'raw user settings' (signalling unprocessed vendor payloads) and that zones are 'in bpm per sport', which is useful context. It does not state return shapes, whether a section can be empty, or what happens if sport is omitted for zone sections.

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?

Very compact and front-loaded — each clause maps to one section value and nothing is wasted. The telegraphic fragment style ('The account owner.') is slightly cryptic, but the structure is efficient for a two-parameter lookup tool.

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?

With no output schema, the description carries the burden of explaining return values, and it only sketches topics rather than shapes or volumes (e.g. how large or how raw 'settings' is). For a simple two-parameter read tool with safety annotations, this is adequate but leaves the agent guessing about the sport/section interaction for zone lookups.

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 coverage is only 50%: the sport parameter is documented in the schema, but the section enum has no per-value description there. The description compensates by explaining what each of the four section values actually returns (measurements/VO2max/threshold/sleep window, raw settings, bpm zones, power zones), which is exactly the meaning the schema lacks.

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 enumerates the four sections (profile, settings, hr_zones, power_zones) and their contents, so an agent can infer this retrieves the account owner's profile data. However, there is no verb at all — 'The account owner.' is a fragment, not a statement of what the tool does — and no differentiation from siblings like garmin_body (which overlaps on body measurements) or garmin_set_hr_zones.

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 is given: nothing says to call this for account-level attributes rather than garmin_body, garmin_status, or garmin_reference. The only implicit routing is the section enumeration, which tells the agent what each section holds but never names an alternative tool or an exclusion.

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