itunes_get_artwork_info

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does reveal the default behavior (falling back to the currently playing track when 'song' is empty), which is useful. However, it does not state that the operation is read-only (though 'Get' implies it), nor does it describe what happens if no artwork is attached, error conditions, or the structure of the returned info. These omissions leave the agent with incomplete transparency about the tool's runtime behavior.

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 extremely concise: a single purpose sentence followed by a clear 'Args' section. It front-loads the core functionality and then provides parameter details in a structured format. There is no redundant or filler content; every word adds value. This is a model of efficient description writing.

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?

Given the tool's simplicity (one optional parameter, read-like operation, no output schema), the description covers the essentials: what it does and how the parameter works. It lacks explicit details about the return format or possible failure modes (e.g., no artwork found), which would improve completeness. However, because the tool is straightforward and the purpose is clear, a 4 is appropriate; the description is not incomplete enough to warrant a 3.

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 description adds substantial meaning to the 'song' parameter beyond the schema. The schema only defines it as a string with a default of '', but the description explains that an empty value triggers inspection of the current track. This context is essential for correct invocation and is not derivable from the schema alone. Since there is exactly one parameter and it is fully explained, the parameter semantics are excellent.

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 action ('Get information') and the specific resource ('attached album artwork for a track'). This unambiguously distinguishes it from sibling tools like itunes_get_track_metadata or itunes_get_lyrics, which target different data types. The verb+resource combination is precise and directly maps to the tool's name.

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 provides clear usage context: the 'song' parameter is optional, and if left empty, the tool inspects the currently playing track. This tells the agent when to use the tool and how to invoke it with or without a specific track. However, it does not explicitly mention alternative tools or when not to use it, so it stops short of a perfect 5.

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