enable_compositor

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

With no annotations provided, the description must disclose behavior, and it does state the exact scene state change (use_nodes=True). However, it does not mention whether the operation is idempotent, whether it clears existing compositor nodes, or any side effect on rendering. For a simple boolean toggle this is adequate but not richly transparent.

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 concise sentence with a useful parenthetical. It is front-loaded with the verb and resource, and every word contributes meaning. No filler or redundant phrasing.

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 that this is a simple no-parameter operation and an output schema exists, the description is mostly complete. It could be improved by noting when to call it (e.g., before creating compositor nodes), but that gap is more about usage guidance than core operational completeness.

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 zero parameters and the schema already covers this fully. The description's parenthetical about use_nodes=True adds a bit of implementation context but is not necessary for parameter understanding. With no parameters, a baseline of 4 is appropriate.

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 ('Enable the compositor') and the underlying implementation ('use_nodes=True on scene'), so an agent knows exactly what operation is performed. It does not explicitly differentiate from sibling tools like get_compositor_tree or setup_basic_composite, but the verb and resource are specific enough to avoid obvious confusion.

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 about when to use this tool versus alternatives such as setup_basic_composite or get_compositor_tree. There is no mention of prerequisites, ordering, or whether this should be called before creating compositor nodes. The agent is left to infer usage context from the sibling list.

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