update_workflow

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

Discloses key behaviors: fetches current version, merges only passed fields, offline validation, and PUT. No annotations exist, so description carries full transparency burden and meets it well.

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 are highly efficient: first explains the full process, second gives a critical usage constraint. No redundancy, front-loaded with purpose.

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?

Covers the update mechanism, validation, and the important replacement behavior for nodes/connections. Lacks explicit note that omitted fields remain unchanged, but it's implied by 'partial update'.

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 low schema description coverage (33%), the description adds significant value by clarifying that nodes/connections replace existing arrays. It names the mergeable fields, but doesn't detail settings or other parameters beyond schema.

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?

Clearly states the verb 'Update' with resource 'workflow partially' and explains the merge mechanism, distinguishing it from a full replacement or other tools like create_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?

Provides explicit instruction to pass full nodes/connections arrays when changing them, but lacks explicit alternatives or when-not scenarios (e.g., when to use create_workflow versus this partial update).

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