add_compositor_node

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 reveals nothing about side effects, whether it requires an existing tree, how it handles node placement, or what the return value is. Essentially no behavioral information beyond a parameter example.

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 brief, but in this case brevity is a sign of under-specification rather than conciseness. It is a raw fragment, not a complete sentence, and it fails to front-load any purposeful content beyond a parameter hint.

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 the tool likely requires existing compositor context and has sibling tools for setup and connection, the description is grossly insufficient. It doesn't explain prerequisites, expected effects, or return behavior, so an agent has no reliable way to invoke it correctly without further inference.

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 adds examples for node_type, which is helpful but incomplete. It covers only one of three parameters (node_type), leaving name and location entirely undocumented. Schema coverage is 0%, so the description must compensate but does so only marginally.

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 a fragment that only gives examples for node_type, not a statement of the tool's purpose. It doesn't explicitly say it adds a compositor node; the function can only be inferred from the tool name and sibling tools. This is vague and fails to differentiate from tools like connect_compositor_nodes or set_compositor_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?

No guidance on when to use this tool, what prerequisites exist (e.g., needing an existing compositor tree via ensure_compositor), or which alternatives are appropriate. The description gives no context for selection among the many compositor-related siblings.

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