Attach To Pure Data Live Session

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

With no annotations, the description carries full burden. It discloses that patchPath is optionally loaded for preview and save, and that attachment is via control/edit ports. But it omits side effects, failure modes, or state changes beyond attachment.

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?

A single sentence that conveys the core function and optional behavior. It is slightly dense but not redundant.

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 covers the essential action and parameter roles for a 3-param tool, but omits usage guidance, side effects, and return information. Given no output schema and no annotations, more context would be expected.

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 has 0% description coverage, so the description must and does explain parameter meaning: control and edit ports are the connection endpoints, and patchPath is the optional patch to load for preview/save. It does not detail constraints, but maps all three parameters.

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 tool attaches to an already-open MCP live-edit Pd patch, specifying the resource and action. It distinguishes from starting a new session by the phrase 'already-open', though it does not explicitly name sibling alternatives.

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 'already-open' implies usage when a live-edit session exists, providing some context. However, it does not explicitly state when not to use it or mention alternatives like pd_start_live_session.

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