Copy track image

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the risk profile is known. The description adds the ownership constraint (both tracks must be 'own' tracks), which is genuine context beyond annotations, but it does not state that an existing image is overwritten or what happens if the source track has no image.

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?

A single efficient sentence with no filler, and the verb plus resource are front-loaded. The 'another own track onto this own track' construction is slightly clumsy but costs little.

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 4-parameter mutation with no output schema, the description covers what is copied, from where, and to where, while annotations carry the destructive/idempotency profile. The main remaining gap is the overwrite semantics for the destination track's existing image.

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 only 50%: `track` and `author` are documented as permalinks, while `from_track_id` (an integer ID) and `kind` have no schema descriptions. The description's 'cover or background' clarifies the `kind` enum values, but it leaves the permalink-vs-numeric-ID distinction between `track`/`author` and `from_track_id` unexplained — a likely source of invocation errors.

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?

States a specific verb (copies) with a specific resource (cover or background image) and both the source and destination track. An agent can distinguish it from set_track_cover and remove_track_cover, though the phrase 'another own track onto this own track' is awkwardly worded.

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?

Usage is implied: reuse an image from another track instead of uploading a new one. No explicit when-not guidance, no mention of the sibling alternatives (set_track_cover, remove_track_cover), and no stated prerequisite that both tracks must belong to the caller beyond the embedded word 'own'.

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