validate_workflow_structure

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

With no annotations provided, the description carries the full burden. It does disclose substantive behavioral content by listing 7 categories of checks the validation performs, which tells the agent what the tool will inspect. However, it omits outcome semantics entirely: whether validation failure throws an exception or returns a report, and whether the tool has any side effects. For a pre-deployment gate, the agent needs to know how to consume the result to decide whether to proceed.

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?

Two sentences with zero wasted words. The first sentence front-loads purpose and timing; the second delivers a compact, high-signal enumeration of checks. Every clause earns its place.

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 tool with fully documented schema and a thorough check list, the description is nearly complete. The notable gap is the absence of an output schema or any description of return values/failure behavior, which matters for an agent using this as a validation gate. But the description covers purpose, timing, and scope thoroughly, so it earns a 4 rather than a 3.

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%, so the baseline is 3, but the description adds real meaning beyond the schema's minimal 'Workflow object to validate.' The check list communicates semantic requirements on the nested workflow fields (node IDs must be unique, node types must be valid, connections must reference valid endpoints, no circular dependencies), which helps the agent construct a valid input or predict what the validator enforces.

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 states a specific verb-action pair ('Validate workflow structure') with an explicit purpose ('before creation/deployment to catch errors early'). The enumerated check list (required fields, unique node IDs, valid connections, circular dependencies, trigger nodes) makes the scope unmistakable and clearly distinguishes it from sibling validation tools like validate_workflow_credentials and validate_workflow_expressions.

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 to use the tool: 'before creation/deployment to catch errors early.' This is clear timing guidance. However, it does not explicitly name alternatives or state when NOT to use it versus the overlapping siblings lint_workflow or validate_workflow_expressions, so it stops short of a 5.

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