set_node_property

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

The description reveals the side effect of saving the scene, which is useful. However, with no annotations, it fails to disclose permission requirements, error behavior (e.g., invalid property paths), reversibility, or impact on unsaved changes.

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, front-loaded sentence with no filler. Every word contributes meaning, making it appropriately concise for the tool's straightforward action.

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?

Given that this is a mutation tool with no annotations, no output schema, and sparse parameter documentation, the description is too terse. It omits important operational context such as how scenes are referenced, what 'serializable' implies for accepted values, and whether the operation is reversible.

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 only 20% (only projectPath is documented). The description adds little beyond the parameter names, mentioning 'serializable' but not explaining how to specify node paths, property names, or valid value types.

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 uses a specific verb ('Set') and resource ('a serializable node property'), and also notes the scene is saved. This clearly distinguishes it from sibling tools like add_node, remove_node, and inspect_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?

No guidance is provided on when to use this tool versus alternatives. The description does not state whether it should be used for modifying existing nodes only, nor does it mention any preconditions or exclusions.

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