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

The description adds substantial behavioral context beyond the annotations: async job_id return, queued-until-desktop-picked-up state, no credits because rendering is local, named failing tracks with reasons, and detailed cancel semantics including refunds and dropped mid-render results. These are exactly the operational details an agent needs before invoking a long-running mutation.

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 dense but front-loaded: the main action and offline/real-plugin distinction come first, followed by constraints and async behavior. The long parentheticals and cancellation detail make it slightly heavier than necessary, though nearly every sentence carries useful information.

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 complex async render tool with no output schema, the description covers the missing pieces: return shape (job_id, later stem URLs), polling tool, queueing dependency on Dø Desktop, track-render limitations, billing, and cancellation behavior. An agent has enough information to invoke and follow up 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 description coverage is already high at 83%, so most parameter meaning is provided structurally. The description reinforces that track_ids can target specific tracks and that results are downloadable stem URLs, but it does not explain format, tail_seconds, or idempotency_key beyond what the schema already says.

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 states a specific verb and resource ('Bounce a session (or specific tracks) to audio') and distinguishes it from generic DAW rendering by explaining that it uses real plugin chains offline. It also differentiates from siblings implicitly by noting that headless renders are audio-only and that instrument/MIDI tracks require Logic open.

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?

It gives clear usage context: offline background rendering via Dø Desktop, headless audio-only limitation, need for Dø Desktop to pick up the job, and polling with doseedo_wait_task. It does not explicitly name alternative sibling tools such as doseedo_mix or doseedo_render_midi, so it stops short of full when-to-use alternative routing.

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