Connect TidalCycles live coding

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which align with the description's 'Create' action. The description adds context about scaffold contents (pattern and orbit maps) but does not disclose whether it creates new components or modifies existing ones, how it interacts with parent_path, or other side effects. No contradiction with annotations, so the lower bar is met with modest additional detail.

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, densely informative sentence. It front-loads the action ('Create') and the resource, with no filler or repetition. Every word contributes to conveying the tool's function.

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?

With 8 parameters and no output schema, the description gives a reasonable overview but leaves questions about what the scaffold actually looks like in TouchDesigner, how the parameters interact, and what the tool returns. The description is adequate for a scaffolding tool but lacks structural details that would fully inform an agent.

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%, so the description should compensate for undocumented parameters. It mentions 'pattern and orbit maps', which loosely relates to pattern_count and orbit_count, but provides no meaning for send_port, receive_port, tidal_host, or active. Parameter names are self-explanatory, but the description adds little semantic value 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 a specific action ('Create') on a specific resource ('TidalCycles/SuperDirt OSC scaffold') and includes the distinctive elements of pattern and orbit maps. This distinguishes it from many 'connect_*' and 'create_*' sibling tools, making its purpose immediately clear.

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 implies usage for live-coded audiovisual sets but does not explicitly state when to choose this tool over alternatives like connect_supercollider_synth or connect_oscquery_namespace. There are no exclusions or comparisons to other connect tools, so guidance is only implied rather than explicit.

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