list_vcv_modules

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

Discloses what information returns in each mode (module slugs, tags, HP widths vs. I/O port names, param names). No annotations exist, so description carries full burden. It doesn't mention error handling or rate limits, but the read-only nature is implied.

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?

Description is informative but slightly verbose. It front-loads the action and uses clear instructions. Could be slightly trimmed, but still efficient for the information conveyed.

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?

Given 2 parameters, 100% schema coverage, and no output schema, description adequately covers modes and supported plugins. Lacks explicit return format or error handling, but is sufficient for typical use. Sibling tools context reinforces need for lookup.

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?

Adds value beyond schema by explaining plugin aliases (e.g., 'mi' for Mutable Instruments) and that module parameter is a slug. Clarifies that omitting module lists all modules. Schema already covers param descriptions, but description enriches usage understanding.

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?

Description specifies 'List available VCV Rack modules and their ports/params for a given plugin' and distinguishes two modes (with/without module). This clearly identifies the tool's purpose and differentiates it from siblings like generate_vcv.

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?

Explicitly states 'ALWAYS call this BEFORE generate_vcv to look up correct module slugs and port names — do NOT guess.' Also lists supported plugins, providing clear guidance on when to use and prerequisites.

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