get_golf_summary

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description goes further and discloses non-obvious behavior: default start/limit values, validation rules that throw GarminError, and the verified fact that the response is a pagination-envelope OBJECT rather than an array. This is genuinely useful disclosure beyond the annotations, though it mentions a `per-page` param that does not appear in the schema, which adds minor confusion.

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?

Purpose is front-loaded in the opening clause, and most of the material is information-dense rather than filler. The second half is a long run-on clause stack with parentheticals, so a minor deduction for readability, but little is truly expendable.

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 correctly shoulders the return-value burden by describing the pagination envelope, and it covers both undocumented parameters. It stops short of saying what fields a scorecard summary row actually contains, so an agent knows the shape of the envelope but not its payload.

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 parameter meaning, and it largely does: it gives defaults (start=0, limit=100) and validation semantics (start non-negative, limit positive, throws on violation). The only gap is that it never states what limit/start physically control beyond pagination offset/count, and the hyphenated `per-page` reference does not map to the schema's `limit`.

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 first clause names a concrete resource ("a page of golf scorecard summaries") and implies the paginated-list verb, so an agent knows it returns summary records. However, it never differentiates itself from close siblings like get_golf_scorecard, get_golf_user_stats, or get_golf_club_stats, leaving the agent to guess which golf resource this is.

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 when-to-use guidance, no prerequisite conditions, and no routing to alternative golf tools. The description explains implementation mechanics (defaults, validation) but never tells the agent under what circumstances this tool is the right choice versus its siblings.

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