blockrun_music

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

No annotations provided, so description carries full burden. It details async polling, payment model (charged only on success, no charge on failure/timeout), models with costs, and permanent URL. This is comprehensive.

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?

The description is concise with 6 sentences, each adding essential information. Core purpose first, then details on duration, polling, payment, models, and return value. No redundant content.

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?

No output schema, but description states 'Returns a permanent BlockRun-hosted URL', which is sufficient. Given complexity (async, polling, payment), it covers key aspects for a music generation tool.

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 100%, baseline 3. Description adds value by providing example prompts, clarifying lyrics cannot be used with instrumental, and stating default values for model and instrumental.

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 clearly states it generates music tracks via BlockRun x402, specifying async and client-polled. It distinguishes from sibling tools by focusing on music generation and detailing output (3 min MP3).

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?

Usage is implied for music generation; the description explains the async nature and polling but does not explicitly state when not to use or provide alternatives. However, sibling tools cover different domains, so it's clear this is for music.

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