set_node_flags

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses two important behaviors: that unspecified flags are left unchanged and that unsupported flags return an 'unsupported' report. However, it does not mention potential side effects, required permissions, or how the result is returned, leaving 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 two concise sentences, immediately stating the action and resource, then adding two key behavioral notes. Every sentence adds value and there is no filler.

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?

The tool has 5 parameters, no annotations, and no output schema. The description covers the core purpose and two behavioral nuances, but it omits details about return values, parameter semantics, and edge cases (e.g., what happens if path is invalid). It is moderately complete but leaves room for agent confusion.

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%, so the description must compensate. It names the flags but does not explain what true/false means for each boolean or the role of the required path parameter. The flags are listed but their semantic meaning is left to inference.

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 function: 'Set node flags' with an explicit list of flag types (display/render/bypass/template). This distinguishes it from sibling tools like set_parameters or set_cop_flags, making the purpose 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?

The description provides useful usage context by explaining that only flags explicitly passed are changed, which helps avoid accidentally resetting other flags. It does not explicitly name alternatives or when-not conditions, but the partial-update guideline clarifies expected behavior.

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