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

Annotations already flag the write/destructive profile, but the description adds material facts the annotations cannot convey: the 2-credit cost, the guarantee that the source song is preserved alongside the new one, and the social precondition of agreeing on style first. The 'keeps the original' phrasing sits in mild tension with destructiveHint=true (which likely refers to irreversible credit spend), but this is not a direct contradiction.

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?

Everything is packed into a single sentence with the routing information ('prefer reimagine_song') front-loaded where an agent will see it first. No filler sentences; only minor awkwardness from compressing four distinct facts into one line.

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?

With an output schema present, return values need not be explained, and the description covers cost, source-song preservation, and the routing decision. It is nearly complete for a two-parameter generative tool; only the minor destructive/credit framing tension leaves a small gap.

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% and both parameters carry their own descriptions, so the schema already does the heavy lifting. The description restates that prompt holds the target style and songId identifies one of the user's songs but adds no format, constraint, or example beyond that, so the 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?

The description states a concrete action on a concrete resource: it makes one of the user's existing songs again in a new style, with new words, and keeps the original. It also distinguishes itself from the sibling reimagine_song by declaring the relationship. It loses a point because the purpose is partly defined by reference to another tool rather than standing on its own.

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?

It explicitly names the preferred alternative (reimagine_song) and the precondition ('agree the style with them first'), so an agent knows both when to pick this tool and when not to. This is exactly the when/when-not/alternative guidance the dimension asks for.

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