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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered and the bar is lower. The description still adds non-obvious behavior: the operation is refused with a 409 while the artist still has songs, which tells the agent to expect a failed call and why.

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 short sentences with zero filler; the core action comes first and the failure condition second. Every clause carries information an agent needs.

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 single-parameter destructive tool with annotations covering safety and no output schema to explain, the description supplies the crucial precondition and error behavior. A minor gap is that it says 'remove' while the tool is named 'archive', leaving the reversibility of the archival ambiguous.

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 there is a single parameter (artist_id), which the schema already documents with type and length bounds. The description implies the target is an artist but adds no syntax, format, or source-of-id detail, so the baseline of 3 applies.

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?

Names a specific verb and resource (remove an artist) plus a scope constraint (one with no songs), so the agent knows exactly what the call does. It does not, however, explicitly differentiate itself from the other artist mutations in the sibling set (rename_artist, create_artist, get_artist), so it falls short of a 5.

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?

Gives a clear precondition for use: the target artist must have no songs. That is effectively a when-to-use criterion an agent can act on, though no alternative tools are named and there is no explicit when-not-to-use guidance for artists that still have songs beyond the stated refusal.

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