Upload release cover art

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

No annotations beyond title, so description carries full burden. Discloses that the operation can replace existing art and that art becomes immutable post-distribution. Could mention file format or size constraints but is adequate.

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 sentences, no wasted words. First sentence defines action, second gives critical constraint. Perfectly front-loaded.

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 simple file upload with two parameters, the description covers purpose, action, and key constraint. No missing context that would confuse an agent.

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 100% with parameter descriptions already present. Description adds minimal extra meaning beyond 'static cover art' context, so baseline 3 is appropriate.

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 'Upload or replace' verb and 'release's static cover art image' resource. Distinguishes from siblings like 'upload_release_asset' and 'upload_track_audio'.

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?

Explicitly warns about immutability after distribution and advises uploading final artwork before distributing. Provides clear timing context but does not explicitly name alternative tools.

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