Drive StreamDiffusionTD

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

The description adds meaningful behavioral details beyond the annotations: it creates a fresh baseCOMP, wires inputs, sets custom parameters, optionally rebroadcasts, returns a friendly error, and includes validated_pars in the result envelope. This aligns with the annotations (readOnly=false, openWorld=true, destructive=false) and provides useful operational context.

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 information-dense with three sentences and no filler. The first sentence is a bit long, but it efficiently covers the setup workflow, error handling, and output envelope. Breaking it into more digestible chunks could improve readability slightly.

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 the tool's complexity (12 parameters, no output schema, open-world external dependency), the description covers the key workflow, error behavior, and result envelope adequately. It does not describe every parameter, but the schema already does, so the description provides enough context for an agent to understand the tool's role and use it appropriately.

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 100%, so the schema already documents each parameter thoroughly. The description adds only a high-level grouping of prompt/strength/cfg/seed and mentions source/top wiring, but does not add new syntax or semantics beyond what is already in 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 tool wraps the StreamDiffusionTD.tox into a one-shot Layer 1 setup, enumerating concrete actions: locate .tox, create baseCOMP, wire input, set pars, and optionally rebroadcast. It distinguishes itself from sibling tools by mentioning downstream consumers like create_ai_mirror that rely on validated_pars.

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 provides clear context about when to use the tool: for one-shot setup of StreamDiffusionTD, with explicit behavior when the .tox is missing (friendly error). However, it does not explicitly state exclusions or alternative tools that should be used instead.

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