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

Annotations already establish it as a safe, read-only, idempotent, non-open-world lookup, so the bar is lower. The description still adds meaningful behavior beyond that: it returns matching tools with descriptions plus an opening link, and it explicitly disclaims that it performs no audio processing — the key trait an agent needs to avoid expecting an action result.

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, front-loaded with the core purpose and followed by the return behavior and the no-processing disclaimer. The long example enumeration is slightly heavy but each item plausibly improves matching for this discovery tool.

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?

The output schema exists, yet the description still usefully summarizes what comes back (matching tools, what each does, a link) and where the user continues the workflow. Combined with 100% schema coverage and clear safety annotations, an agent has everything needed to call this 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 description coverage is 100% and the single 'task' parameter is already documented with examples, so the schema carries the load. The description's task list overlaps the schema examples and adds thematic breadth but no new syntax, format, or constraint guidance, so baseline 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?

States a specific verb and resource ('Finds the SongUp AI browser audio tool') and enumerates concrete task categories (stem splitting, karaoke, mashup, noise removal, mastering, chord detection, MIDI conversion, auto-tune), making the scope unmistakable. This is clearly distinguishable from siblings like find_songs and start_custom_song, which concern songs rather than AI audio tooling.

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?

The description gives clear trigger context — use it when the user 'describes' an audio task — and adds an explicit when-not caveat: 'This tool does not process audio itself,' directing actual work to songupai.com. It does not explicitly route to sibling tools, which keeps it short of a 5.

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