Update a track

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

Annotations are minimal (only title), but the description adds meaningful behavioral context: partial update (supply only fields to change) and field locking based on release state. No contradiction with annotations.

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 efficient sentences: first states purpose, second adds behavioral note. Front-loaded and no wasted words.

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?

Covers purpose, partial update, and locking behavior. Lacks explicit mention of return value (e.g., updated track object) and does not explain success/error responses. Adequate for a simple update tool but could be more complete.

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 50%; description reinforces that 'fields' should contain only changing values and references create_track for the full schema. Does not enumerate possible fields or constraints on the nested object, leaving some ambiguity.

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?

Clearly states it updates track metadata and mentions 'supply only the fields you want to change', which distinguishes from create_track. However, it does not explicitly differentiate from other update tools like update_release or update_artist.

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?

Provides context that some fields lock after release submission/distribution, implying when not to use it (or that certain fields become immutable). Does not explicitly state when to use this tool versus alternatives or provide exclusions.

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