Set Node Graph Port Value

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

The description reveals the internal payload building and type coercion for vectors, which adds some value. However, it does not discuss return values, error handling, or mutation persistence, leaving gaps given no annotations.

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?

Three front-loaded sentences, each earning its place: purpose, relation to sibling, and a key type detail. No extraneous text.

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 no output schema and no annotations, the description lacks info on return values and error scenarios. Schema covers params, but guidance on targeting the material graph (scope vs handle) is minimal.

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?

With 100% schema coverage, baseline is 3. The description adds extra meaning by clarifying that 3-number arrays become maxon.Vector and providing port path examples, going beyond the schema.

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 'Update a single port on a node' with a specific verb and resource. It distinguishes itself from apply_graph_description by positioning as a thin convenience, and from set_xpresso_port by targeting material graphs.

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 explains it is a convenience over apply_graph_description, implying when to use it. However, it lacks explicit when-not-to-use or alternative scenarios like setting multiple ports.

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