validate_workflow

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

With no annotations provided, the description carries the full burden, and it delivers: it discloses that an invalid workflow is a normal return, that a missing 'valid' key means 'not cleared', that findings keys are optional, and that raising means no verdict. It also lists known blind spots, which is exactly the kind of behavioral context an agent needs beyond the schema.

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 longer than average, but every section earns its place: the return contract, the error semantics, and the gotchas are all decision-relevant. It is front-loaded with the core purpose and return contract before the gotchas. Slightly dense, but not padded.

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?

For a single-parameter validation tool with no output schema and no annotations, the description is remarkably complete. It explains the return shape, error semantics, and known blind spots, so an agent can call it and interpret the result correctly. Nothing critical is missing.

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. It names the single parameter implicitly via the wrapped command ('--workflow <path>') and the required 'workflow_path' is clear from the schema. It doesn't describe path format or accepted file types, but with only one parameter and the workflow-path semantics evident from the tool name and description, the gap is minor.

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 opens with a specific verb ('Pre-flight') and resource ('a workflow against the live local ComfyUI'), and immediately distinguishes it from running the workflow. It names the wrapped CLI command and the checks performed (class_types, input shapes, enums, wiring), so an agent can tell it apart from siblings like run_workflow or vary_workflow.

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 frames this as a pre-flight step before running, and the 'Gotchas' section gives concrete conditions for interpreting results (e.g., a pass does not guarantee server acceptance, watch for non_node_key warnings, no allocation estimate). It also clarifies when raising means no verdict came back, which is strong when-to-use and how-to-interpret guidance.

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