auto_lofi_effect

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

With no annotations provided, the description carries full burden and discloses key behavioral traits: it runs as a background job, returns a job_id for monitoring, and details the internal audio processing chain. It lacks explicit mention of whether the operation is destructive or creates new audio files, but covers the async execution model thoroughly.

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?

Information is well-structured with clear sections for behavior, technical pipeline, arguments, and warnings. The 'CREATIVE LO-FI EFFECT:' prefix is slightly redundant but functional. Each sentence provides distinct value about behavior, parameters, or constraints.

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 an async pipeline tool with no output schema, the description is complete. It explains the return value (job_id), references the sibling monitoring tool, documents the sole parameter fully, and describes both the technical process and artistic result.

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 0% (intensity parameter has no description or enum), but the description fully compensates by documenting the valid values ('light', 'medium', 'heavy'), their semantic meanings ('subtle warmth', 'classic lo-fi', 'extreme tape sound'), and the default value.

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 applies a 'vintage/lo-fi sound' and distinguishes itself from generic audio effects by detailing the specific processing pipeline (HPF > LPF > bass/treble warmth > compression). The specific audio characteristics ('warm, muffled, vintage') clarify the output quality.

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?

Explicitly states when NOT to use the tool ('DO NOT call this again if a pipeline is already running') and names the specific alternative tool to use instead ('use check_pipeline_status'). Also clarifies the async pattern: 'returns a job_id immediately. Use check_pipeline_status to monitor.'

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