garmin_records

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, yet it only restates the data returned ('activity details and dates') — content the output schema already defines. It says nothing about read-only semantics, authentication/account requirements, data freshness, or whether records are user-scoped, all of which an agent would want to know before calling.

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, front-loaded sentence that identifies the resource and its payload with no filler. It is efficient, though it is lean to the point of omitting any usage or scope context.

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?

For a zero-parameter tool with an output schema, the description covers the essentials (what the records are and that they include dates/details) and the schema handles return structure. However, it omits scope and freshness context — e.g., whether PRs are all-time or per-activity-type — that would make the definition fully self-sufficient.

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 zero parameters, so the baseline of 4 applies; there is no parameter semantics to clarify and no ambiguity the description could resolve.

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 a concrete resource ('personal records (PRs)') and the enrichment it carries ('activity details and dates'), so an agent knows exactly what data comes back. The verb is only implied ('All ... records'), and it does not explicitly distinguish itself from siblings like garmin_activities or garmin_goals, but the resource is specific enough to identify.

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 statement of when to call this versus alternatives such as garmin_activities or garmin_goals, nor any prerequisite (e.g., sync freshness) or scope caveat (all-time vs. recent). The agent must infer usage entirely from the resource name.

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