download_album

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

Discloses external dependency (tidal-dl-ng), separate authentication, potential download time, error handling guidance, and return format. No annotations exist, so the description fully bears this burden.

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, when to use, prerequisites, after-use steps, args, and returns. All sentences add value, though slightly verbose. Front-loaded with main action.

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?

Given one parameter, no output schema, and low schema coverage, the description is remarkably thorough: covers purpose, prerequisites, usage, behavior, error handling, and return value. Very complete.

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 schema provides minimal description (type string, title). The description's 'Args' section adds clear semantics: 'The TIDAL album ID to download (numeric string)', compensating for 0% schema coverage.

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?

Clearly states it downloads a TIDAL album to local storage using tidal-dl-ng. Provides specific user requests that should trigger this tool, distinguishing it from siblings like download_track or download_playlist.

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 lists when to use the tool with example queries and important prerequisites (installation, authentication). Lacks explicit 'when not to use' but provides comprehensive context.

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