Recommend TIDAL tracks

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

Annotations only declare readOnlyHint and openWorldHint; the description adds behavior beyond them: deduplication, deterministic metadata filters, explicit non-support for mood/acoustic API filters, and which dimensions are enforced (year, duration, explicitness, exclusions, per-artist diversity). This discloses the tool's processing contract.

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?

Three tight sentences with the tool action front-loaded and no filler; each sentence adds distinct information (what it does, what is not filterable, what is enforced).

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?

Output schema exists, so return values need not be described, and annotations cover read-only/open-world status. However, for a 4-parameter recommendation tool with nested filters, the description omits guidance on seed count, result limits, and per-seed limits, leaving the agent to infer practical call sizing from the schema alone.

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 only 25%, and the description names broad categories of enforced filters (year, duration, explicitness, exclusions, diversity) that correspond to some filter properties, but it does not explain top-level max_results, limit_per_seed, or seed_track_ids behavior beyond the one schema description. It partially compensates but leaves important controls undocumented.

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 chain ('Get ... deduplicate ... apply filters') and resource (Track Radio candidates), and notes that deterministic filtering is applied here. It does not explicitly name siblings like tidal_get_track_radio or tidal_get_track_radio_mix to differentiate, so not a 5.

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?

Gives context about what filters are enforced and what is left to the calling model's assessment, which implies use when deterministic metadata filtering is needed. But it does not state when to choose this over tidal_get_track_radio, tidal_get_track_radio_mix, or search, and no when-not alternative is named.

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