set_multiple_nodes_property

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states that it sets a property, which implies mutation, but it omits important details such as error handling for invalid nodeIds or property names, whether the operation is atomic, any permissions needed, or rate limits. This lack of behavioral context is a significant gap for a mutation tool without annotations.

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 extremely concise: two sentences, 19 words. It front-loads the action in the first sentence and provides usage context in the second. Every word contributes meaning without repetition or filler. This is an excellent example of efficient communication.

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 simplicity, the description covers the core action and typical use cases. However, it lacks details on return values (no output schema, so the description should hint at what happens after execution) and error handling. It also does not mention any constraints like maximum number of nodeIds. While adequate for a straightforward setter, it leaves some gaps for an AI agent to fully understand 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?

Schema coverage is 100% with all three parameters described. The property parameter includes examples (e.g., 'visible', 'opacity'), which adds slight value beyond the schema. The value parameter only says 'Value to set for the property,' which is generic but adequate given the dynamic nature. As baseline is 3 due to high coverage, the description does not significantly enhance meaning, so 3 is appropriate.

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 tool's purpose: setting a property value on multiple nodes simultaneously. It provides concrete examples of properties like visibility, opacity, or position, and the verb 'Set' plus resource 'multiple nodes' is specific and unambiguous. The name itself reinforces this, and it distinguishes from single-node or different property tools.

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?

The description includes 'Useful for bulk updates like visibility, opacity, or position,' which implies when to use it—for bulk operations. However, it does not specify when not to use it (e.g., for complex conditional updates) or offer alternatives like execute_batch or individual setters. The guidance is implicit rather than explicit, scoring 3.

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