set_node_properties

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

The description discloses key behavioral traits: it modifies the scene file on disk and changes are permanent. This goes beyond the sparse annotations (all false hints) and adds context about persistence and file mutation. It does not discuss potential side effects like overwriting existing properties, but the explicit 'permanently' and 'on disk' provide meaningful transparency.

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 extremely concise: two sentences, with the first stating the core purpose and the second giving the alternative. Every word earns its place, and the main information is front-loaded.

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 straightforward mutation tool with no output schema, the description covers the essential context: what it does, where it acts (disk), and when not to use it. It lacks details on return values or error handling, but these are not critical for a set operation and the tool is simple enough (4 required params, full schema descriptions) to be considered adequately complete.

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?

The schema provides full descriptions for all four parameters, so baseline is 3. The tool description does not add any additional parameter-level detail beyond what the schema already documents, such as value formats or examples.

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 properties on a node in a saved scene file (.tscn) on disk permanently.' This specifies the verb (Set), resource (properties on a node in a scene file), and scope (on disk permanently). It also distinguishes from the sibling tool set_property by pointing to the alternative for live runtime changes.

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?

Usage guidance is explicit: 'For live runtime changes, use set_property instead.' This tells the agent exactly when to use this tool vs. the alternative, making the decision process straightforward.

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