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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data's provenance (belongs to those third-party apps, neither Morris's nor official), the 20-item cap, and the prohibition on folding it into handicap calculations. It does not describe ordering or what happens when no imports exist, which keeps it short of a 5.

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?

Three sentences, front-loaded with the resource and scope, followed by the trigger and the exclusion. Dense but every clause earns its place; the 'screenshots, import_rounds, log_practice' parenthetical is slightly list-heavy but informative about sources.

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?

A zero-parameter, read-only tool with no output schema needs the description to say what comes back and what it means. This definition does exactly that: imported rounds and practice sessions, their cap, the player's preferred app, and the caveat that the figures are third-party and excluded from official stats.

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 no parameters, so there is no parameter semantics to explain and the baseline applies. The description does clarify what the fixed output scope is (latest 20 imported rounds/practice sessions plus the player's stated app), which is a small bonus.

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 precise verb+resource: reading rounds and practice sessions imported from other golf apps, plus the app the player keeps rounds in, capped at the latest 20. It explicitly separates this data from list_rounds, get_round_history and the handicap, so the agent can distinguish it from every sibling that returns round data.

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?

Gives an explicit trigger ('Use it when they mention another app') and an explicit exclusion ('not in list_rounds, get_round_history or the handicap, so never mix them in'), naming the alternatives directly. Both when-to-use and when-not-to-use are covered.

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