blockrun_music

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

The description discloses significant behavioral traits beyond the annotations: it is async and client-polled, takes 1-3 minutes, charges only on success, and returns a permanent URL. This adds transparency about side effects and failure modes that the annotations (readOnlyHint=false, destructiveHint=false) do not convey.

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 well-structured and concise, front-loading the core purpose and then adding essential operational details (duration, polling, payment, model, return type). Every sentence contributes value without redundancy or excessive length.

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 tool's complexity (async, money-related, time-consuming), the description is remarkably complete. It explains the asynchronous flow, payment settlement policy, time estimate, and return format (permanent URL). No output schema exists, so the description adequately fills the gap.

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 input schema already has 100% parameter description coverage, so the baseline is 3. The tool description adds minimal parameter-specific meaning (e.g., model cost) but mostly relies on the schema. It does not need to compensate for missing parameter documentation.

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, specifically full-length ~3 minute MP3s, via BlockRun x402. It identifies the distinct resource (music) and differentiates from sibling tools like blockrun_image and blockrun_speech by naming the output type and model.

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 provides useful context such as async processing, polling behavior, and payment terms, but does not explicitly state when to use this tool over alternatives or when not to use it. Usage is implied by the tool name and purpose rather than directly guided.

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