itunes_edit_track_metadata

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that an empty song means the currently playing track and that fields are optional, but it does not mention side effects, whether unspecified tags are left untouched, error behavior, or persistence.

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 opens with a one-sentence purpose and then lists each parameter in a compact Args block. It is concise, scannable, and contains no filler.

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 six-parameter mutation tool with no annotations or output schema, the description covers the input semantics and primary behavior. It lacks some operational details like confirmation or error behavior, but the tool's scope is simple enough that this is a minor gap.

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 explains all six parameters in plain language (e.g., 'New genre tag', 'Release year') despite the schema having no property descriptions. This effectively compensates for the 0% schema coverage, though it adds no format or constraint details.

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 starts with 'Edit and update metadata tags on a track in your library,' clearly identifying the action and target resource. This differentiates it from sibling read/metadata tools like itunes_get_track_metadata and itunes_set_track_bpm.

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 implies its use for modifying track metadata and notes that an empty song targets the currently playing track. However, it does not explicitly specify when to choose this over related metadata/set tools or any prerequisites/limitations.

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