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

The description goes well beyond the annotations by disclosing in-place node updates via existingNodeId, lead preservation for claimed nodes, the NODE_HAS_ACTIVE_LEADS error and how to resolve it, validation behavior, and atomicity ('Invalid graphs are rejected and the workflow is left unchanged'). No annotation contradiction is present.

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 every sentence carries distinct, necessary information: core action, parameter grouping, node semantics, failure mode, validation behavior, and sibling tool routing. It is front-loaded with the primary purpose and contains no filler.

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 behavior well, but for a complex mutation tool with an empty schema it omits a critical piece: how the agent specifies which workflow to update (e.g., a workflowId parameter). Without that, and with no schema or output schema to fill the gap, the description is not complete enough for correct invocation.

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?

With an empty input schema, the description is the only source of parameter meaning: name/description/emailGoogleAccountId for metadata and graph/existingNodeId for graph replacement. However, it does not specify types, requiredness, the graph node structure, or how the target workflow is identified, so an agent still lacks enough structural detail to invoke the tool reliably.

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 clear verb ('update') and a specific resource ('workflow's name, description, email sending account, and/or graph'), immediately distinguishing this from sibling tools. It also names the one sibling it is not (campaignstack_update_workflow_status), which removes ambiguity.

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 explicitly separates metadata patching from graph replacement and says both can be combined in one call. It also gives an explicit when-not-to-use instruction: 'To enable or disable a workflow use campaignstack_update_workflow_status instead.' This is clear routing behavior.

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