compositor-add_node

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

No annotations are providedainer. The description only states the action with no mention of side effects, requirements, or behavior. It doesn't disclose that it likely adds a node to the active compositor tree, nor any error conditions or return values. With no annotations, the description should convey these but does not, so it's a significant gap.

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?

One sentence, no redundancy, front-loaded with action. Very concise.

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?

The tool is a mutating operation on a compositor node tree, but the description doesn't mention prerequisites (active compositor?), side effects, or how it interacts with other compositor tools. It's too terse for a tool with a required parameter.

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 has two parameters (name, type) with no description and 0% schema description coverage. The tool description does not mention them at all. It does not explain what 'type' expects or how 'name' is used. The description fails to add any meaning beyond the parameter names.

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 'Add a node' and the resource 'scene compositor node tree'. It is specific enough to distinguish from other add-node tools like shading-add_node, though it could mention it's for the compositor specifically (which it does). Minor lack of detail about what kind of node or where it goes, but still clear.

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 on when to use this tool versus alternatives. It doesn't mention preconditions (e.g., need an active compositor scene), or scenarios where this tool is appropriate. Sibling tools like shading-add_node or geometry_nodes-add_node are not mentioned. No exclusions or context given.

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