geometry_nodes.set_node_input

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

The description discloses no behavioral traits. It does not mention side effects (e.g., overwriting existing socket values), prerequisites (e.g., an active geometry node group), or permission requirements. Annotations already indicate readOnly=false and destructive=false, but the description adds no context. 'Risk: standard' is safety metadata, not behavior.

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 short but under-specified rather than concise. The statements about risk and maturity may be operational metadata, but they do not help an agent select or invoke the tool. The functional purpose is missing entirely, so the brevity is a liability, not a strength.

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 tool with 8 parametersilet, an output schema, and a specific operation (setting a node input), this description is severely incomplete. It fails to explain the operation's scope, the meaning of the socket and value parameters, or how it fits into broader geometry node workflows. An agent cannot confidently use this tool based on the description alone.

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 description provides zero information about parameters. The input schema has 8 parameters with only 50% coverage (value has a description; _requestId, _authorization, _transactionId have descriptions; node, socket, groupName, _expectedSceneRevision do not). Since the description doesn't compensate for the missing schema coverage, the agent has no additional semantic hints about what these parameters mean or how they relate.

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 is essentially a tautology: it states the command name 'geometry_nodes.set_node_input' and adds non-functional metadata (risk, maturity, requirements). It never explicitly says 'sets the value of a socket on a geometry node', so an agent must infer the action solely from the name. This fails to distinguish from sibling geometry node tools or clarify the operation.

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 about when to use this tool versus alternatives like geometry_nodes_set_modifier_input or geometry_nodes_inspect. The note about 'Per-request argument checks and session policy still apply' is a constraint, not a usage recommendation. The agent is left to guess the appropriate context.

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