blockrun_music

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

The description discloses async behavior, client-polling, completion time (1–3 minutes), and the payment model (only charged on success). Annotations are sparse, so the description carries the full burden and delivers rich behavioral context.

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 and well-structured: purpose first, then process details, model pricing, and return type. Every sentence adds necessary information without fluff.

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 the 5 parameters and no output schema, the description provides sufficient context (return type, async process, pricing). It covers the tool's lifecycle and constraints adequately.

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 description coverage is 100%, but the description adds value by listing models with pricing and noting that lyrics cannot be used with instrumental: true, which is not fully captured in the schema.

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 the tool generates music tracks via BlockRun x402, specifying it produces full-length ~3 minute MP3 files. This verb+resource pairing is distinct from sibling tools like blockrun_image or blockrun_video.

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 music generation but does not explicitly state when to use this tool over alternatives or when not to use it. No sibling comparison is provided, and no exclusion criteria are given.

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