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

With no annotations, the description carries the full burden and does so thoroughly: it discloses the 202 + job id flow, polling getApiJob, the 50-generation queue limit, 429 PENDING_JOBS_LIMIT, credit cost, and required API key scope. It is slightly marred by the internal tension between 'no separate polling step' and the later instruction to poll getApiJob, but the behavioral detail is otherwise strong.

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 long but dense and front-loaded with purpose and result shape. Nearly every sentence carries operational value, though the repeated polling guidance and the internal inconsistency around polling add mild redundancy and confusion.

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?

Despite having no annotations and no output schema, the description is remarkably complete: it covers input expectations, asynchronous behavior, polling steps, rate limiting, error code, credits, auth scope, and sibling-tool routing. An agent has enough information to invoke and monitor this 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics: duration 0 means auto-pick based on the description, duration is capped at 10 seconds, and request_id can be used to locate the result via the assets endpoint. These additions go beyond the schema field descriptions.

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 opens with a specific verb and resource: 'Produce a looping background ambiance soundscape from a text description,' reinforced by concrete examples. It further distinguishes the tool from nearby siblings by naming createSoundEffect, createMusic, and createAudioTransform as alternatives.

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?

Explicit usage guidance is present: 'Use this for continuous, atmospheric background loops; use createSoundEffect for short discrete sound effects, createMusic for musical pieces, and createAudioTransform to remix an existing audio sample.' It also explains the async flow, so an agent knows exactly when to call this and when to poll getApiJob.

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