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

The description is highly transparent: it states real side effects ('the target node really executes'), warns against write/send/payment nodes, explains auto-mocking and missing upstream behavior, details sequential execution, and clarifies tool-metadata returns for agent-wired nodes. It aligns with destructiveHint=true and adds substantial behavioral detail beyond annotations.

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 dense but well-organized: purpose first, key execution semantics next, side-effect warning prominently, then return format. No redundant filler; every sentence adds useful information.

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?

The description covers the essential context an agent needs: what the tool does, how predecessor nodes are handled, side effects, sequencing, agent-wiring behavior, and output structure. It is complete for the tool's complexity, even without a formal output schema.

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?

The schema has 0% description coverage, but the description compensates partially: it clarifies return_output=true vs truncated preview and explains node execution semantics. workflow_id and node_ids are not individually described in prose, though their roles are inferable from 'Run specific nodes in a workflow' and the schema names.

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's purpose: 'Run specific nodes in a workflow for testing.' It identifies the resource (workflow nodes), the action (run), and the intended context (testing), distinguishing it from full-workflow 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?

The description gives good usage guidance by specifying 'for testing', explaining predecessor auto-mocking behavior, and prominently warning about side effects. It could be slightly stronger by explicitly contrasting with run_workflow, but the intent is clear enough for an agent to choose this tool appropriately.

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