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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds value by explaining the two-step behavior (save image, optionally assign to target), but it does not disclose whether assignment overwrites existing artwork or whether deletion is possible later.

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 sentence that packs the source, action, output, and optional assignment without fluff. It is efficiently front-loaded and every word contributes to understanding the tool's operation.

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 presence of a full input schema with 100% coverage and an output schema, the description covers the workflow context well. It lacks only minor guidance on prerequisites such as job completion status, but the explicit reference to droptrack_get_ai_job makes the intent clear enough.

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 description coverage is 100%, and each parameter is already explained in the input schema. The description merely restates the target type without adding new semantic details about jobId, candidateId, assign, or targetType.

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 uses a specific verb ('Save') and names the exact resource (an AI album artwork candidate from droptrack_get_ai_job), the resulting artifact (a reusable DropTrack image), and the optional target (track or playlist). This clearly distinguishes it from siblings like droptrack_generate_album_art and droptrack_delete_album_art_image.

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 clearly implies the usage context: after obtaining candidates via droptrack_get_ai_job, this tool accepts one. It does not explicitly mention when not to use it or name alternatives, so it misses the full 'when-not/alternatives' bar.

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