Create SAM2 segmentation bridge

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds useful behavioral detail by listing the created subcomponents and explicitly noting that no model is bundled, setting accurate expectations. It does not mention potential side effects like overwriting existing containers or network calls, but the annotation coverage reduces the burden.

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 two sentences: the first states the high-level action, the second lists deliverables and the no-model caveat. Every word earns its place with no redundancy.

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 rich schema and annotations cover most operational details. The description gives a good overview of what will be created but omits information about return values or prerequisites (e.g., external service must be running), which is not covered elsewhere. For a tool with 9 parameters and external service integration, slightly more context would be helpful, but the current level is adequate.

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?

All 9 parameters are fully described in the schema (100% coverage), so the description does not need to elaborate. It provides context that the bridge is for an external SAM2/FastSAM service but does not add syntax or format details beyond what the schema already provides.

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 builds a TouchDesigner bridge surface for an external SAM2/FastSAM segmentation service and enumerates the specific components it creates (source input, mask receiver, mask_out, matte_out, preview_out). This precise verb+resource combination distinguishes it from sibling creation tools.

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 external SAM2/FastSAM segmentation integration but does not explicitly state when to use it over alternatives or provide exclusions. No comparison with similar bridge tools such as connect_comfyui or create_external_io is provided.

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