list_library_playlists

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds the authenticated account context and implies a read-only list operation, but does not state side effects, return format, or error conditions. This is minimal behavioral disclosure.

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 in Spanish that front-loads the action and object. It contains no redundant information and is well-structured.

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 one-parameter list tool, the description conveys the core function and the authentication context. However, it omits explanation of the limit parameter and return value structure, which could matter in the absence of an output schema and annotations. A more complete description would clarify pagination and result format.

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 schema has one parameter, limit, with no description, and the tool description provides no explanation of its meaning. Since schema description coverage is 0%, the description fails to compensate, leaving the agent to infer that limit controls the number of returned playlists.

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 playlists from the authenticated account's library, using a specific verb and resource. It distinguishes from sibling tools like list_liked_songs and get_playlist by explicitly naming 'playlists' and 'biblioteca'.

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?

No guidance is provided about when to use this tool versus alternatives such as get_playlist or search_music. The description does not mention any exclusions, criteria, or context for selection.

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