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

Annotations already declare this a safe, non-destructive, closed read, so the description only needs added context — and it supplies the sort order and the shape of each record, which annotations cannot express. It stops short of disclosing pagination or what happens past the 50-item cap, but for a read-only list this is solid added value.

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 sentences with no waste: scope and return fields first, then the handoff to get_song. Every clause carries information an agent needs.

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 usefully enumerates the returned fields and their order, which is the main thing an agent would otherwise lack. It is only marginally incomplete on result-count/pagination behavior beyond the limit parameter.

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 coverage is 100%, and the limit parameter is already documented with its default and 1-50 bounds in the schema. The description adds no additional meaning about the limit, 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?

Names the specific resource (songs on the person's Daydream account), the ordering (newest first), and the exact fields returned (id, words, length, tempo, version count). It also explicitly separates itself from get_song, so an agent can pick between list and single-item retrieval without opening a 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?

Explicitly routes the agent to get_song with an id when the goal is to play a song, which is the key branch point among siblings. It does not address the other siblings (get_songs_left, create_song, the stem tools), so coverage of alternatives is partial rather than complete.

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