run_workflow_url

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

With no annotations, the description fully carries the burden, disclosing SSRF protection, timeout/size limits, read-only default, conversion process, and execution behavior when run=true.

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?

Well-structured single paragraph, front-loading the main action. Slightly dense but not overly verbose; could be split for readability.

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 complexity (fetch, convert, validate, optionally execute), the description covers all necessary aspects including security, error handling, modes, and parameter overrides. No output schema, but return of prompt_id when run=true is mentioned.

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 coverage is 100%, and the description adds meaning beyond schema by explaining input overrides behavior, common keys, and clarifying the default false for run.

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?

Clearly states 'Read (and optionally execute) a shared ComfyUI workflow from a URL', using specific verb and resource, and distinguishes from siblings like get_workflow by describing URL-based fetching and optional execution.

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?

Explains when to use run=true vs false, lists supported URL types, and gives error guidance for unsupported hosts. Could be more explicit about when to use this vs other tools, but the context implies the distinction.

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