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

Discloses supported formats (WAV/MP3/FLAC/OGG), streaming download with timeout, default save location (/tmp), and return values (path, size, suggestion). No annotations provided, so description carries full burden. Lacks details on error handling or overwrite behavior, but core behavior is well covered.

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?

Well-structured with sections for purpose, pipeline context, supported formats, parameter details, return value, and examples. Front-loaded with core function. Some redundancy (e.g., examples repeated), but overall efficient.

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?

Covers purpose, usage, parameters, return, and next steps. Assumes output schema exists for return value details (not shown). Missing explicit error handling or edge cases, but for a download tool, the description is sufficiently complete for agent decision-making.

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 has 0% description coverage; description fully compensates by explaining each parameter: url (direct URL from AI generator), filename (default derived from URL), output_dir (must exist, default /tmp). Examples demonstrate usage with custom filenames.

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?

Clear verb ('download'), resource ('audio file from URL'), and context (bridges AI generators and DAW). Distinguishes from siblings by explaining its position in the pipeline: generate track → get URL → download → import audio. Examples reinforce purpose.

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 states when to use (after generating a track, before import_audio_to_tracks) and provides alternatives (manual curl/wget). Includes examples with specific use cases (Suno tracks) and next steps.

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