geometry_nodes.set_modifier_input

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

Annotations already indicate this is not read-only, not idempotent, and not destructive, but the description adds no behavioral context beyond generic 'Risk: standard' and 'maturity: L3'. It does not disclose side effects, transaction expectations, or mutation semantics, so the agent gains little insight into what invoking this tool will do.

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 it spends its only sentence on a restatement of the command name and generic risk metadata rather than useful tool behavior. This is under-specification, not effective conciseness.

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 non-read-only, non-idempotent tool with 8 parameters and no parameter guidance, the description is almost entirely uninformative. It omits what the operation does, when to use it, how parameters relate, and any behavioral expectations, leaving the agent without the context needed to call it correctly.

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 50%, and several key parameters such as object, socket, and modifierName have no descriptions. The tool description provides zero parameter-level meaning, so it does not compensate for the schema gaps.

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 only restates the tool name ('PartMe Blender Harness command `geometry_nodes.set_modifier_input`') and adds risk/maturity boilerplate; it does not explain what setting a modifier input does. The verb/resource are inferable from the title, but the description itself is essentially tautological and does not distinguish this from siblings like geometry_nodes_set_node_input.

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?

There is no guidance about when to use this tool versus alternatives, no mention of prerequisites, and no exclusion criteria. The only requirement statement ('Per-request argument checks and session policy still apply') is generic policy, not usage direction.

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