set_compositor_node_input

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not indicate that this is a mutation operation, whether it requires existing nodes, side effects (e.g., overwriting values), or error conditions. The name suggests setting an input, but no behavioral specifics are disclosed.

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 sentence that repeats the tool name. This is severe under-specification, not conciseness. No valuable content is present to earn its place; it conveys no information beyond the identifier.

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 that sets a compositor node input, an agent needs to know how to identify the node, what input names are allowed, and what value formats are valid. None of this is provided. The lack of any operational context makes this tool nearly uncallable without external knowledge.

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 input schema has 3 parameters (node_name, input_name, value) with 0% description coverage. The description adds no meaning to these parameters. It fails to explain what node_name references, what input names are valid, what value types are accepted, or how they relate. The description provides zero assistance in understanding the parameters.

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 'Blender Studio Pro MCP: set_compositor_node_input', which is merely the tool name prefixed with 'Blender Studio Pro MCP:'. It states no verb, resource, or scope beyond what the name implies. This is a tautology and provides no additional clarity for distinguishing it from siblings like get_compositor_tree or add_compositor_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. There is no mention of prerequisites (e.g., an existing compositor node), interactions with get_compositor_tree or connect_compositor_nodes, or condition exclusions. The description offers no usage context whatsoever.

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