Bulk Update Nodes

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

With no annotations, the description carries the full burden. It does convey blast radius ('every node matching a set of filters'), which is useful, but a bulk write tool should disclose reversibility, whether updates merge or overwrite existing field values, transaction semantics, and permission requirements — none of which appear.

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?

A single front-loaded sentence with no waste, and the scoping condition is stated plainly. It is efficient, though its brevity contributes to the behavioral gaps noted elsewhere.

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?

An output schema exists, so return values need not be explained, and all three params are schema-documented. However, for a bulk mutation with zero annotations, the description omits the safety and semantic context an agent needs to call it responsibly.

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 description coverage is 100%, so the schema already documents all three parameters; baseline 3 is appropriate. The description adds no syntax or format detail (e.g. filter operators, expected update value shape) beyond what the schema provides.

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?

States a specific verb (apply), resource (nodes), and scope (every node matching a set of filters), which clearly separates it from the single-record update_node sibling. It does not name the alternative explicitly, but the 'bulk' framing and filter-based selection make the intent unambiguous.

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 on when to use this versus update_node or query_nodes, and no prerequisites stated. There is no warning about the irreversible, wide-blast-radius nature of a bulk mutation, leaving the agent to infer usage conditions.

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