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

The annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the description carries real extra weight: it discloses credit cost (2 per style, 3 per style over 3:30), latency ('takes a few minutes'), async behavior (returns a job id), and a persistent side effect (results save to the member's Gen library). It does not say whether credits are consumed on failure or how to cancel a job, so it is short of a 5.

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?

One dense but well front-loaded paragraph: eligibility, action, cost, then follow-up tooling. Every clause carries information, though the stacked parentheticals ('(2 per style, 3 per style for songs over 3:30)') make it slightly hard to scan.

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 no output schema, the description still covers the return (a job id consumed by check_transform) and the persistence side effect, plus cost, latency, eligibility, and the cheaper alternative. An agent has everything needed to decide and invoke correctly.

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%, so the baseline is 3; however the description adds meaning beyond the schema by tying credit consumption to the styles parameter count and describing direction as free-form 'plain words' creative guidance. It still doesn't clarify the song identifier resolution order (id vs. link vs. title) that the schema only lists.

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 and resource ('render NEW versions of a catalog song in chosen production styles, keeping the original vocal') and pins down scope with the eligibility qualifier 'For a connected Starchild member.' It is immediately distinguishable from change_style (existing styles) and check_transform (job polling).

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 routes the agent: 'Use change_style first for styles that already exist (free),' and names check_transform as the follow-up for the returned job id. It also states the precondition (connected member) and the cost condition, so the when-to-use decision is fully specified.

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