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

With annotations only saying non-readonly, non-destructive, open-world, the description adds substantial behavioral context beyond them: asynchronous job lifecycle, the transfer REPORT fields (`report`, `lossy`, `summary[]`, `warnings[]`), asymmetric target formats (Cubase/Studio One/Bitwig → .dawproject, Dorico → MusicXML), known lossiness (Cubase .cpr lacks audio pool, Dorico .dorico lacks notes), and the credit-refund rule. None of this contradicts the annotations.

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?

Purpose is front-loaded, but the remainder is a single dense paragraph of parenthetical clauses where critical operational steps (upload flow, async waiting, cancel/refund) are buried mid-text rather than surfaced. Every sentence carries information, but the lack of structure makes it harder to scan than its length warrants.

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, high-variance conversion tool with no output schema, the description covers input prep, direction semantics, target-format asymmetries, expected report fields, async handling, and failure/refund behavior. An agent has everything needed to invoke it correctly and interpret results.

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 operational meaning beyond the schema for project_key — zip a project folder so audio travels, a bare file also works, multipart past ~4 GB — and names the exact direction string pattern and per-family asymmetry. It does not, however, add much to the options object that the schema doesn't already spell out.

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?

Starts with 'DAW CONVERTER: a project rebuilt natively in the target' — a specific verb and resource — and enumerates exactly what travels (tracks, MIDI, audio clips, tempo, markers, plus automation/buses/plugin state for certain pairs). It explicitly distinguishes itself from doseedo_import_project (editing) and from session-based conversion, so an agent can tell it apart from siblings without opening schemas.

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 routing: 'To EDIT a project use doseedo_import_project; to convert a session the tools built: doseedo_download_session → upload that zip → logic2<target> (not a session_id).' It also states the prerequisite ('Upload first: doseedo_get_project_upload_url + PUT'), the async follow-up (job_id → doseedo_wait_task), and the no-stop cancel semantics, leaving little to inference.

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