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

Annotations already declare readOnly/non-destructive/closed-world, so the safety profile is covered; the description adds genuinely new context—no-account requirement for listing versus shared allowance for processing—plus the practical guidance to hand the website link to the user when upload isn't possible. It doesn't mention rate limits or catalog size, but the important behavioral traits are disclosed.

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?

A single front-loaded sentence with the usage trigger first, followed by the tool inventory and return contents. The parenthetical list of synonyms (vocal remover, acapella, karaoke instrumental) is slightly verbose but earns its place for matching user phrasing.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes the key fields (id, accepted formats, website link) and gives the downstream action to take with them. For a parameterless listing tool with full annotation coverage, nothing an agent needs is missing.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly implies a parameterless catalog call without introducing any false input expectations.

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 ('see NiceVois's free audio tools') and then enumerates the actual tool categories (vocal split, lead/backing split, noise removal, de-reverb). This makes it clearly distinguishable from the sibling processing tools like create_free_audio_job and get_free_audio_job, which act on a single job rather than cataloging options.

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 frames discovery vs. processing ('discovery needs no account; processing shares your account allowance') and gives a concrete trigger ('when you cannot upload their file yourself'). It stops short of naming the sibling to call after discovery, but the when-to-use condition is clear.

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