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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavior: the operation consumes credits and requires the generate permission. It stops short of saying what the destructive aspect actually destroys (e.g., prior node output) or how failures are surfaced.

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 tight sentences with no filler; the core action and its input sourcing come first, followed by the permission requirement. Every clause carries 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?

For a three-parameter mutation with no output schema, the description covers cost, permission, and input semantics adequately, and annotations carry the safety hints. Minor gaps remain around failure behavior and which node state is overwritten.

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 only 33% – only idempotencyKey is documented. The description never explains what workflowId or nodeId select, nor that nodeId must reference a node with saved config and resolvable upstream outputs, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('generate one generation node') plus the precise inputs it draws from ('its saved config and the latest successful outputs of its upstream nodes'). This is unambiguous and clearly distinct from the workflow-level siblings like create_workflow or apply_workflow_change.

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?

It states a prerequisite ('Requires the generate permission') and an implicit cost gate ('Spend credits'), which is useful context. However, it never says when to prefer this over alternatives such as apply_workflow_change or a whole-workflow run, and no exclusions are given.

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