list_zyn_presets

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It clearly indicates a non-destructive list operation by using the verb 'List', and describes the category filtering behavior. It does not mention potential side effects, but for a simple listing tool none are expected. The description could have added context about where presets are sourced, but the core behavioral profile is transparent enough.

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 concise and front-loaded. The main action is stated in the first sentence, with the parameter details presented in a compact Args block. Every sentence earns its place, and there is no redundant or filler content. The structure is easy for an agent to parse quickly.

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 tool with a single optional parameter and an output schema available, the description is complete. It covers the operation's purpose, the parameter's optionality, example values, and the default behavior (omit to list all). Since the output schema exists, returning the list format need not be described. No critical information is missing for correct invocation.

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 0%, so the description must fully compensate for the parameter's meaning. It does this well: 'category' is explained as an optional filter, with concrete examples ('Bass', 'Strings') and an explicit statement that omitting it lists all categories. This adds substantial semantic value beyond the bare schema definition, making the parameter's role unmistakable.

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 opens with a specific verb and resource: 'List available ZynAddSubFX presets (.xiz files)'. This clearly identifies the operation as a read-only query for preset files, which is distinct from sibling tools like load_zyn_preset or set_zyn_params. The purpose is immediately comprehensible and not a tautology.

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 gives clear context on how to use the tool, including the optional category filter with examples and the instruction to omit it for all categories. It does not explicitly compare itself to sibling tools, but the listing operation is inherently distinct from loading or modifying presets, so exclusion guidance is not critical here. The usage context is sufficient for an agent to decide when to call it.

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