Update Workspace Node

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

Discloses the internal fetch-merge-write behavior, merge vs replacement semantics, and forbidden fields (overrideSQL). Annotations indicate idempotentHint=true and destructiveHint=false, which is consistent. No contradiction.

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 concise, front-loaded with the core purpose, and uses efficient sentences. Every sentence adds essential information without redundancy.

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?

Given the presence of an output schema and the tool's complexity, the description adequately covers the update process, merge semantics, forbidden fields, and references to external resources. No gaps in requirements or behavior.

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 input schema already provides 100% description coverage for parameters. The description adds value by clarifying the changes parameter structure ('Partial node fields...'), emphasizing array replacement vs object merge, and listing common fields. This enhances understanding beyond the 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?

The description clearly states the action (update) and resource (workspace node), explains the safe fetch-merge-write approach, and distinguishes from sibling tools like replace_workspace_node_columns by providing a specific alternative. It includes explicit mention of object deep-merge and array replacement.

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 when-to-use and when-not-to-use guidance, including a warning against using overrideSQL/override.* fields and a pointer to list_workspaces for finding workspace IDs. Also suggests an alternative tool for complex column transformations.

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