auto_lofi_effect

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

With no annotations, the description carries the transparency burden. It discloses asynchronous behavior ('runs in background — returns a job_id immediately'), the processing pipeline, and a concurrency warning. However, it does not state whether the effect modifies the original audio in place, replaces it, or operates only on the current selection.

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 organized: purpose, background behavior, pipeline, argument details, and a final warning. It is scannable and each section is useful, though there is some redundancy between the opening description and the later explanation of cutting highs and boosting low-mids.

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?

For a single-optional-parameter tool with no output schema, the description covers invocation, return value, monitoring pathway, concurrency constraints, and parameter semantics. Missing details are selection scope and what exactly happens after the job completes, but the reference to check_pipeline_status reduces the impact of that 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 schema provides only an unconstrained 'intensity' string with a default and no enum or description. The prose fully documents all accepted values ('light', 'medium', 'heavy'), their intended sonic character, and the default, completely compensating for the 0% schema description 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 clearly states the tool's purpose: 'Apply a vintage/lo-fi sound to your audio' and names it a 'CREATIVE LO-FI EFFECT.' The pipeline details and audio character help distinguish it from sibling effect tools, though it does not explicitly contrast itself with similar effects like equalization or filtering.

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 gives explicit operational guidance: 'Use check_pipeline_status to monitor' and 'DO NOT call this again if a pipeline is already running — use check_pipeline_status instead.' This is a clear when-not with a named alternative, but it does not discuss when to prefer a different effect tool over this one.

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