render_stems

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

The annotation 'destructiveHint: true' already signals destructiveness. The description adds the 'sequential solo' behavioral detail, but does not disclose other traits like file overwriting or required permissions. The mention of feeding into another tool is also useful.

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 single sentence is concise and front-loaded, but it sacrifices essential parameter information. The description could be structured to include key details without expanding significantly.

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 an output schema, the description omits return value details and does not explain how the stems are used by 'analyze_audio_character'. The missing parameter semantics further reduce completeness.

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 has one required parameter 'out_dir' with no description, and schema coverage is 0%. The tool description does not mention 'out_dir' at all, leaving the agent with no guide on what value to provide.

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 it renders per-track stems and mentions the method (sequential solo). It distinguishes from sibling 'render_project' by focusing on individual tracks. However, it could be more explicit about what 'stems' are and how it differs from 'render_and_audit'.

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 as a precursor to 'analyze_audio_character', giving context for when to use it. However, it lacks explicit when-not-to-use guidance and does not compare to alternatives like 'render_project' or 'render_and_audit'.

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