set_node_groups

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

No annotations are provided, so the description is the sole source of behavioral disclosure. It reveals the critical behavior that groups not in the desired set are removed, which is important for a setter. However, it does not mention prerequisites, side effects on related nodes, or error handling, leaving some transparency gaps.

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, well-structured sentence with no fluff. It front-loads the core action (set full group membership) and adds necessary clarification. Excellent brevity and clarity.

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?

For a mutation tool with no annotations, no output schema, and low parameter coverage, the description is sparse. It explains the core action but lacks usage guidance, parameter format details, and edge-case behavior, making it insufficient for confident invocation without additional information.

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 0%, and the description only loosely maps to the parameters ('node' and 'groups'). It does not explain node_path's expected format (e.g., full path vs node name) or whether groups are created if they don't already exist. The description fails to compensate for the lack of schema descriptions.

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: to set a node's full group membership, with 'adding and removing to match the desired set' specifying that it replaces the current set. This distinguishes it from siblings like get_node_groups (read-only) and batch_add_nodes (likely additive only).

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 'full' modifier implies this tool is for replacing all group memberships, but no explicit alternatives or exclusions are given. The description does not state when to prefer this over batch_add_nodes or find_nodes_in_group, leaving usage context only implied.

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