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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: results include listen links and cover art, and the data is illustrative sample content rather than customer records — a provenance fact an agent could otherwise get wrong. It does not mention result count, ordering, or whether the full set is always returned.

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?

Two short sentences with zero filler; the payload description comes first and the important provenance caveat follows immediately. Nothing is repeated from the schema or annotations.

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 simple, read-only, single-optional-parameter list tool with no output schema, the description covers what is returned and the nature of the data. Minor gaps remain around result volume and whether filtering by occasion narrows or expands results, but nothing blocks a correct call.

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% — the single optional 'occasion' parameter is already documented with examples (Christmas, Mother's Day). The description adds no further meaning about how the filter matches or what happens when it is omitted, so the 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?

The description names the resource concretely — example Wisheroo songs, each with a listen link and cover art — so an agent knows exactly what comes back. It also disambiguates the data's nature (samples built from example memories, not customer songs). It stops short of an explicit verb like 'list all', but the resource and payload are unmistakable and clearly distinct from start_song_link or list_products.

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?

Usage is only implied: this is the tool for browsing sample/demo songs, and the caveat that these are 'not customer songs' steers the agent away from treating results as real customer data. There is no explicit when-to-use vs. when-not, and no sibling is named as an alternative (e.g., list_occasions for filtering by occasion, start_song_link for actual playback flows).

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