compositor-enable

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

Since no annotations are provided, the description carries the full burden. It only states the action 'enable or disable' without disclosing any side effects, such as whether disabling nodes affects rendering output, or whether it requires a specific selection or mode. The behavior is plain but lacks depth.

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, immediate and precise, with no redundant words. It is highly efficient and appropriately sized for the tool's simplicity.

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 very simple tool (one boolean parameter), the description is minimally adequate, but it lacks crucial context such as whether this affects the entire compositor or just selected nodes, and whether it has effects on rendering. The absence of an output schema and annotations makes the incomplete description more noticeable.

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 schema has a single boolean parameter 'enable' with a title, but the description does not explicitly connect this parameter to the operation. It implies toggling but never mentions the parameter name or its role, failing to add beyond the schema's limited title.

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 or disable) and the resource (scene compositor nodes), and it is distinct from sibling tools like compositor-add_node or compositor-link, which handle different aspects of compositor operations.

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 usage guidance is provided. It does not specify when to use this tool versus alternatives, such as whether it applies to the active scene or globally, or under what circumstances one would enable or disable compositor nodes.

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