select_synth

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

With no annotations provided, the description carries full burden. It discloses the trade-off of pattern filtering (faster loading vs. limited subsequent operations) and lists known synth options. However, it omits details about error handling, persistence of selection across sessions, or side effects like unloading previous presets.

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 well-structured: first sentence states purpose and requirement, second sentence explains the optional pattern and trade-off, followed by a bullet list of known synths. No unnecessary verbiage; every sentence earns its place.

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 description lacks information about the output or return value (no output schema exists). It does not explain what happens after selection (e.g., presets loaded into context, potential side effects like unloading previous synth's presets). Given the complexity and reliance on this tool by siblings, more completeness is needed.

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 input schema already covers both parameters with 100% description coverage. The description adds value by providing usage context for the pattern parameter (glob pattern example, trade-off explanation) and listing all known synth values in text, enhancing the schema's enum.

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 'Select a synth and load its preset library' and distinguishes itself from sibling tools like list_synths (which only lists synths) and get_current_synth (which gets current selection). It also notes that it must be called before other preset tools, reinforcing its unique role.

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 explicitly states 'MUST be called before other preset tools' and explains when to use the pattern parameter (for faster loading with large libraries) vs. omitting it (recommended for full access). It provides clear context but does not explicitly exclude alternatives or mention when not to use the tool.

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