set_node_flags

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

No annotations are provided, so the description carries the full disclosure burden for a mutation tool. It implies a boolean flag toggle but does not state whether changes require specific permissions, whether they persist, how null/default values behave (all params default to null), or what the response contains.

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 wasted words. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined pruning.

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 format need not be described, but with no annotations and 0% schema description coverage across four parameters, the description should do more. It omits flag semantics, default/null behavior, and any usage context for a mutation tool.

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 schema provides no descriptions, so the description must compensate. It does name the three flag parameters (display, render, bypass) and identifies the target ('a node', i.e., node_path), but it adds no meaning about what each flag does or what an unset/null value means.

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 pairs a specific verb ('Set') with a specific resource ('flags on a node') and enumerates the three flag categories (display, render, bypass). It is clear what the tool does, though it does not explicitly distinguish itself from nearby mutators like set_parameter or modify_node.

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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of alternatives such as set_parameter or modify_node, which could also alter node state. The agent must infer that this is the right tool for toggling visibility/render/bypass flags.

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