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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds a lot on top: the note budget (inline at ≤200 notes, otherwise note_count + notes_omitted:true), track-level pagination via `truncated` + `next` with the exact continuation args, and the `sync.live_edits` flag answering whether an edit reaches Logic now. These are real behavioral traits an agent cannot infer from structured fields.

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?

Front-loaded and information-dense, but delivered as one sprawling run-on with stacked parentheticals that is hard to scan. Little is redundant, yet the structure could be split into purpose / return shape / budget sections without losing content.

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?

There is no output schema, so the description must carry the return shape, and it does — field-by-field including wire id formats, units (beats and seconds), and truncation semantics. For a read tool with a large nested payload this is as complete as an agent needs to call it 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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: `i` is the identifier edit_midi_notes selects by, param_id is required by set_device_param, and include_params:false / include_automation:false degrade to counts. It also states that tempo, markers, buses and sync are always returned even when `tracks` filters.

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?

Opens with a specific verb and resource ("Read a DAW session") and frames the tool's role as "the arrangement an agent edits against," which distinguishes it from doseedo_edit_session and doseedo_list_sessions. The enumeration of returned fields makes the contract unmistakable.

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?

Clear guidance: call this to get the arrangement, take the ids and "Pass the ids straight to doseedo_edit_session," and consult doseedo_edit_ops_reference {section:"summary"} for the field map. It also implies session_id comes from doseedo_list_sessions. No explicit when-not-to-use statement, which keeps it at 4 rather than 5.

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