Connect TidalCycles live coding

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description's 'Create' aligns with a non-read-only operation. The description adds that it builds a scaffold with pattern and orbit maps, which gives some sense of the generated structure. However, it does not disclose side effects such as potential overwriting at parent_path or external dependencies like a running SuperDirt instance.

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 a single sentence of about 15 words, front-loading the main verb and object. It is concise, avoids redundancy, and every word contributes meaning.

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 gives a clear high-level purpose but lacks details about the scaffold's internal structure, prerequisites, and behavior. As a creation tool with 8 parameters and no output schema, more specifics about what gets created and any requirements would improve completeness, though the core intent is clear.

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 only 38% (3 of 8 parameters have descriptions). The description mentions 'pattern' and 'orbit' which loosely relate to pattern_count and orbit_count, but it does not compensate for the majority of undocumented parameters like send_port, receive_port, active, etc. The parameter names are self-explanatory, but the description adds little semantic depth beyond the schema.

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 the action ('Create a TidalCycles/SuperDirt OSC scaffold') and the specific resource ('pattern and orbit maps') for live-coded audiovisual sets. It distinguishes itself from sibling connectivity tools by naming the exact technology and the scaffold nature of the operation.

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 phrase 'for live-coded audiovisual sets' provides implied usage context, but the description does not explicitly mention when to use this tool over alternatives like connect_supercollider_synth, nor does it state prerequisites or exclusions. There is no differentiation from similar OSC bridge tools.

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