editor_set_node_properties

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It specifies that properties are set but does not state whether existing properties are overwritten, whether invalid property names cause errors, whether the operation is atomic, or any side effects. This leaves significant behavioral ambiguity for a mutating tool.

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 a single, clear sentence with no wasted words. It is appropriately sized for a simple setter, though it is minimal and lacks depth. It is not bloated, but could have included more behavioral context without sacrificing conciseness.

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 tool's moderate complexity (batch mutation, no annotations, no output schema, two parameters), the description is too thin. It does not explain what 'properties' means in this context, how the batch operation behaves, or why an agent would choose this over specialized setters. The schema compensates for parameter names but not for operational context.

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 fully describes both parameters ('Node path' and 'Properties to set'), so schema coverage is 100%. The description adds the notion of 'multiple' and 'at once', but provides no additional semantic detail beyond what the schema already states, such as property value types or handling of nested objects.

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 'Set multiple properties on a node at once' clearly states the action (set), the target (node properties), and a key differentiator ('multiple at once') that distinguishes it from single-property setters like set_node_position. It is specific enough to convey the tool's core function, though 'properties' remains somewhat generic without schema context.

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?

No guidance is provided on when to use this tool versus alternatives such as modify_node or the many editor_set_*_param tools. There is no mention of prerequisites, contexts, or exclusions, leaving the agent to infer when batch-setting properties is appropriate.

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