list_parameters

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

No annotations are provided, so the description carries the burden. It discloses that this is a read-style reference lookup and describes the categories of information returned, but says nothing about permissions, freshness/caching, or whether results are static. For a zero-parameter lookup tool this is strong but not fully complete.

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 sentences, front-loaded with what the tool returns, followed by the actionable usage instruction. No filler, and the operative guidance ('call before write_patch/edit_patch') is placed where an agent will read it.

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?

An output schema exists, so return-value documentation is not strictly required, yet the description still summarizes the payload categories, which is exactly what an agent needs to decide whether to consult it. Nothing required to invoke a no-arg reference tool 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?

The tool takes no input parameters, so per the rubric the baseline is 4 and there is nothing further to document. Schema coverage is 100% with an empty object, so no parameter semantics are missing.

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 (parameter reference) and enumerates what it returns: settable names, ranges/options, Init values, modulation sources/destinations, and factory wavetables. It also explicitly distinguishes itself from the write_patch/edit_patch siblings, so an agent can identify it without opening the schema.

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 an explicit trigger condition ('Call this whenever you're unsure of an exact name, range or option') and names the sibling tools it should precede (write_patch/edit_patch). This is textbook when-to-use guidance with the alternative workflow spelled out.

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