set_node_flags

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

With no annotations supplied, the description carries the full behavioral burden and discloses nothing: not that this mutates node state, not whether display/render flags are mutually exclusive within a network, not whether the change is undoable, and not what a null flag argument does. The single sentence adds zero context beyond the tool name.

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?

It is short with no wasted clauses, but this is under-specification rather than conciseness: one four-word sentence is front-loaded with nothing useful and omits the information the agent needs. Brevity here costs more than it saves.

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 six-parameter mutation tool with no annotations, no output schema, and no documented parameters, the definition is far too thin. It should at minimum enumerate the flag types and state that omitted or null flags are left untouched.

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 0% across six parameters, so the schema offers only bare titles. The description's word "flags" loosely links the five boolean parameters to the operation, but it never explains the tri-state null default (presumably "leave unchanged") or the exclusivity semantics of display versus render, which is the most likely source of misuse.

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 has a verb ("Set") and a resource ("flags on a node"), which is more than a restated name, but "flags" is never enumerated. An agent cannot tell from the text whether this covers bypass/lock/render/display/template or some other flag family, so the boundary against set_node_color, set_node_position, or change_node_type is only inferable from those siblings' names.

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 mention of prerequisites, and no reference to alternatives such as set_node_color for appearance or change_node_type for node kind. The agent must guess that this is the tool for toggling bypass/lock/display/render/template state.

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