geonodes_set_input

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

No annotations are provided, so the description must bear full responsibility. It states 'set ... default value' but does not disclose behavioral details such as mutation permanence, overwriting existing connections, or error handling. The tool is clearly a mutation, yet no side effects or safety information is conveyed.

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: one sentence followed by a bullet list of four parameters. It is front-loaded with the essential purpose, and every line serves a clear function. No wasted 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 annotations, no output schema, and a 4-parameter tool, the description is incomplete. It omits information about return values, success/failure indications, prerequisites (e.g., tree must be editable), and any constraints. While it covers the basics, it lacks the depth needed for reliable use.

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 includes a parameter list with brief semantics for each argument (e.g., 'tree_name: Node tree name'), adding meaning beyond the bare schema which has no descriptions. However, the 'value' parameter type is vague ('float, int, vector list, etc.'), and the description lacks format details. With 0% schema coverage, this partially compensates but could be richer.

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 action ('Set') and the resource ('a node input's default value'). It is distinct from sibling geonodes tools like 'geonodes_add_node' or 'geonodes_connect'. The verb and resource are specific and 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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., the node or node tree must exist). It only states what it does, leaving the agent to infer usage context.

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