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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), yet the description adds non-obvious context the annotations cannot convey: the first RFEG call creates the report and its short link and persists nothing else, and a no_report sentinel is returned when none exists. The create-on-first-call behavior sits in mild tension with readOnlyHint, but the description pre-empts that by framing it as the only thing ever saved, so it reads as clarification rather than contradiction. It stops short of describing the 'few key facts' payload, which would need an output schema to be fully covered.

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 the purpose front-loaded, followed by usage routing and then behavioral caveats in descending priority. Minor deduction: "which is all it ever saves" is slightly oblique and the "few key facts" phrase is left dangling.

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 one-parameter, fully documented enum tool with no output schema, the description supplies purpose, routing, the creation side effect, and the empty-case signal — enough to call it correctly. The only gap is that the returned facts are not characterized, though the absence of an output schema makes that a modest omission.

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 100% and the single source parameter is a fully documented enum, so the schema already does the heavy lifting. The description restates the three report sources but adds no format, default, or error-handling detail beyond it, so baseline 3 applies.

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?

"Get a short link to one of the player's ready-made reports" names a specific verb and resource, then enumerates the three concrete report sources (RFEG handicap, TrackMan sessions, Garmin rounds). It explicitly separates itself from get_reports, which reads report data, so the agent can route without opening either schema.

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?

"Use it to share or open the report; to read the report's data use get_reports" states both the intended use and the condition that selects the sibling alternative. That is a direct when/when-not routing rule rather than implied usage.

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