list_liked_songs

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

No annotations are present, so the description must convey behavioral traits. It mentions the ability to filter by text, artist, or album, which adds context, but does not explicitly state read-only behavior, pagination, or authentication requirements. The verb 'Lista' implies a read operation, but the lack of explicit safety disclosure prevents a higher score.

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?

The description is a single, concise sentence with no redundancy. It front-loads the primary action 'Lista canciones' and efficiently adds filter capabilities without unnecessary detail.

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?

The tool has no output schema and no annotations, so the description must cover key aspects. It adequately indicates the tool returns a list of liked songs and supports filters, but lacks details on the limit parameter, result format, and user/library scope, leaving some gaps for a simple list tool.

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 input schema has 0% description coverage, but the description explains the meaning of three filter parameters ('texto', 'artista', 'album') corresponding to query, artist, and album. However, the 'limit' parameter is not addressed, leaving part of the parameter semantics undocumented.

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 clearly states the tool lists liked songs with filtering by text, artist, or album. The verb 'Lista' and resource 'canciones marcadas con Me gusta' are specific, and it distinguishes from siblings like list_library_playlists (playlists) and search_music (search).

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?

The description does not specify when to use this tool versus alternatives, nor does it provide exclusions. It simply states what the tool does, leaving usage context to be inferred from the purpose.

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