Get a track audio download URL

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

Description goes beyond readOnlyHint annotation by revealing that the URL expires in ~10 minutes, should be fetched directly without API token, and returns specific fields. No contradiction with annotations.

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 sentences effectively cover purpose, parameter detail, and usage warning. Front-loaded with key action, no redundancy.

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 two parameters, readOnly annotation, and no output schema, the description fully explains return structure and behavior. No gaps for an agent to use the tool 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?

The description elaborates on asset_type values (WAV master vs MP3 preview), adding meaning beyond the schema's enum list. For track_id, no extra info, but overall adds value given 50% 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?

The description explicitly states the tool returns a time-limited signed URL to download a track's audio asset. The verb 'return' and resource 'download URL' are clear, and it distinguishes itself from sibling tools like get_track or get_track_file.

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 implies usage for obtaining download URLs of audio assets. While it doesn't explicitly mention when not to use it or provide alternatives, the context of sibling tools makes the use case clear.

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