params_list

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningful behavior: the scope includes both instrument and insert-effect parameters, plugin tracks can have hundreds of entries, and the page size defaults to 100 — all useful for anticipating result size.

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?

Two tight sentences: the first defines scope and return fields, the second gives the narrowing/paging strategy. The field list is dense but front-loaded and no sentence is filler.

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?

With no output schema, the description correctly compensates by naming the returned fields (key, name, device, group, range, default, current value), and it covers pagination defaults. Track identifier semantics are left to the schema, which documents them fully, so nothing essential is missing.

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 baseline is 3. The description still earns a bump by explaining that filter words must ALL match (conjunctive semantics) and giving a concrete example ('filter cutoff'), plus restating the default page size in context of why paging matters.

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 names the resource precisely (every parameter of a track, covering the instrument and all insert effects, plugins included) and enumerates the returned fields. It's clear it's a read/list operation and distinct from params_set or devices_get, though the verb itself is only implied rather than stated.

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 concrete guidance on narrowing with filter and paging with offset/limit for plugin-heavy tracks, which is real usage advice. But it never says when to reach for this versus siblings like devices_get, automation_list, or params_set, leaving tool selection to inference.

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