list_presets

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

No annotations are present, so the description carries the full burden. The verb 'list' implies a read-only operation, and the description adds that it returns names, categories, and authors. This is sufficient for a non-destructive tool, though it could explicitly state it does not modify any state.

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 two sentences with no wasted words. It is front-loaded with the primary action and details. Every sentence adds value: the first explains what it does, the second gives usage context.

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?

The tool is simple (list presets with fields), and the description covers the key aspects: what is returned (names, categories, authors), a prerequisite (synth selected), and a use case (browsing). It does not explain pagination beyond what the schema provides, which is acceptable. No output schema is present, but the return values are implied.

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 100%, so the baseline is 3. The tool description does not add any extra meaning beyond what the schema already provides for 'limit' and 'offset'. The schema descriptions are adequate on their own.

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 clearly states 'List all loaded presets for the current synth with their names, categories, and authors.' It uses a specific verb ('list') and identifies the resource ('presets') and the fields returned. This distinguishes it from sibling tools like search_presets or filter_presets.

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?

The description says 'Use this for browsing available presets' and adds a prerequisite 'Requires a synth to be selected first.' This gives a clear use case and condition. However, it does not explicitly mention when not to use this tool or suggest alternatives like filter_presets for refined queries.

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