get_compositor_tree

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

There are no annotations, so the description must disclose behavioral traits on its own. It fails to state whether this operation is read-only, what the return structure looks like, whether it may throw errors, or any side effects. The description provides zero behavioral information beyond the name.

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 short, but it is under-specified rather than appropriately concise. It is a single phrase with no structure, no front-loading of useful information, and no attempt to guide the agent. It reads as a placeholder rather than a deliberate, minimal description.

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?

While an output schema exists, the description gives no context about the compositor tree's structure, its relationship to other compositor tools, or any caveats. For a tool with significant implications (understanding a node graph), the description is woefully inadequate. It does not help an agent know what to expect or how the result should be interpreted.

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 tool has 0 parameters, so there is nothing to explain. Per the rubric, a 0-parameter tool receives a baseline of 4. The description does not need to add parameter detail, and it does not.

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 'Blender Studio Pro MCP: get_compositor_tree' essentially restates the tool name with a context prefix. It identifies the resource ('compositor_tree') and the verb 'get' implies retrieval, but it adds no additional clarification about what the tree represents or what exactly is returned. It is slightly more than a pure tautology but still does almost nothing to differentiate the tool from siblings.

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. Sibling tools like ensure_compositor, add_compositor_node, and set_compositor_node_input relate to compositor operations, but the description offers no hint about when get_compositor_tree is the right choice or any prerequisites.

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