port_workflow

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

Annotations indicate readOnlyHint=false and destructiveHint=false, consistent with the description which details modifications (swaps, retunes, etc.) without claiming read-only or destructive behavior. The description adds behavioral context beyond annotations by listing specific changes and the return format with flags, though it does not mention any additional risks or edges.

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 compact and front-loaded with the essential purpose. It efficiently conveys scope, exclusions, and results in a few sentences. Minor density could be improved, but overall it is well-structured with no wasted words.

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 (model porting between families) and the presence of an output schema and annotations, the description covers the core functionality, usage boundaries, and outputs. It lacks explicit mention of prerequisites or detailed parameter ranges, but the context provided is largely sufficient for a qualified 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 0%, so the description must compensate. While the overall description implies the role of target_family via the example, it does not provide explicit details about the parameters' meaning, allowed values, or format. The parameter names are self-explanatory to some extent, but the description misses an opportunity to add semantic depth.

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 explicitly states 'CROSS-FAMILY MODEL PORT ONLY (e.g. "sdxl" -> "flux")' and details the operations performed (swaps loader topology, retunes CFG/steps/sampler/scheduler, etc.), making the tool's specific verb+resource clear and distinguishing it from siblings like diagnose_workflow and resolve_missing_nodes.

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 explicitly states when NOT to use the tool ('NOT for fixing missing/uninstalled nodes - that's diagnose_workflow + resolve_missing_nodes'), providing clear exclusions and alternative tools. It also indicates the tool returns changes and flags for judgment, guiding the agent on what to expect.

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