garmin_user_profile

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about whether the call is read-only, whether it requires authentication/consent, or what scope of profile data is returned. Because there are zero parameters, the risk of a destructive action is low, but the omission of any behavioral context is still a gap.

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, waste-free sentence that front-loads the resource. It is appropriately sized but arguably under-specified rather than genuinely concise, which keeps it out of the top band.

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 the description need not explain return values, and the tool's zero-parameter simplicity limits what must be covered. Still, given the crowded sibling namespace, the absence of any routing or usage cue leaves the definition only minimally complete.

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 tool takes no parameters and schema description coverage is 100%, so there is nothing for the description to clarify. Baseline of 4 applies for a zero-parameter tool.

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 names the resource ('User profile and settings') and locates it in Garmin Connect, which distinguishes it from siblings like garmin_devices, garmin_goals, or garmin_hr_zones. However, it supplies no verb or action, so an agent must infer that this is a retrieval tool rather than a settings-mutation tool. Purpose is implied but not stated.

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?

There is no indication of when to call this tool, what triggers it, or how it differs in use from the many other Garmin data tools. No alternatives are named despite ~48 sibling tools. The agent is left to infer usage entirely from the name.

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