garmin_api_profile

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false). The description adds genuinely useful behavioral context — that the response may contain account identifiers and PII and that raw JSON fields are unnormalized — which goes beyond the annotations. However, the trailing sentence about date-range defaults and 31-day limits describes constraints that cannot apply to a zero-parameter tool, introducing confusion rather than transparency.

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?

Four short sentences with no filler, and the PII disclosure is well placed early. The final sentence, however, is off-topic for this tool and does not earn its place — it reads as boilerplate carried over from a range-based sibling.

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 structure needn't be explained, and the PII/raw-JSON warnings usefully prepare the agent for the payload. But the contradictory date-range sentence leaves an unresolved question about whether the tool actually accepts filtering, which is exactly the ambiguity the description should have eliminated.

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 schema takes zero parameters, which would normally earn the baseline 4. But the description discusses date-range defaults and 31-day caps, implying configuration that does not exist in the schema — actively misleading for a parameterless call rather than merely additive.

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?

"Full profile settings" identifies the resource but omits a verb, leaving it ambiguous whether the tool fetches, updates, or describes settings. The profile resource is genuinely distinct from the activity/sleep/wellness siblings, so an agent can locate it, but the absence of an explicit action verb keeps this at minimum-viable.

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 guidance on when to call this versus the 30+ sibling tools, and no prerequisites or exclusions are stated. An agent must infer from the tool name alone that this is the account-profile endpoint rather than a health-metric endpoint.

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