get_user_summary

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's '(Garmin Connect, read-only...)' merely restates that. Beyond the date format, it adds no behavioral context such as what the summary aggregates, freshness of data, or unit conventions.

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?

It is short and front-loaded with the action, but the date format appears twice ('YYYY-MM-DD' and 'Dates are YYYY-MM-DD') and the parenthetical mixes redundant safety restatement with the format note, wasting the limited space available.

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-value shape needn't be explained, and annotations cover the safety profile. Still, for a tool sitting among dozens of overlapping daily-summary and statistics calls, the description leaves the core question — what this summary contains that the others don't — unanswered.

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 0%, so the description must carry the load: it does clarify that 'cdate' is a date in YYYY-MM-DD, which is real added meaning over the bare string property. However, it says nothing about acceptable ranges, timezone interpretation, or what happens with dates lacking data, so the compensation is partial.

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 verb and resource ('Return user activity summary') and pins the required date format, but 'user activity summary' is never defined and is indistinguishable from siblings like get_user_statistics, get_daily_summaries, or get_today. An agent cannot tell from this text which of those overlapping summary tools to pick.

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 guidance on when to use this versus the many neighboring summary/statistics tools, and no stated prerequisites or exclusions. Usage is only implied by the single-parameter signature.

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