compositor.enable

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

With no annotations, the description must disclose behaviors like side effects, scope (active scene?), or prerequisites. It only restates the function without revealing impacts, such as whether existing nodes are preserved or if state is persisted.

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?

Single sentence, no redundant words. Front-loaded with verb and resource. Efficient for a simple tool.

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 one-parameter boolean tool with no output schema, the description is minimally adequate. However, it lacks completeness on usage context and behavioral transparency, which are important for an agent to use it correctly.

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 0% description coverage, so the description should explain the 'enable' parameter beyond its name and type. The phrase 'Enable or disable' adds minimal value since the parameter name is self-explanatory. No default behavior or meaning of 'true' vs 'false' is clarified.

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 explicitly states the action (enable/disable) and the resource (scene compositor nodes). It clearly differentiates from sibling tools like compositor.add_node or compositor.report, which have different purposes.

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, such as when specific nodes need to be toggled individually, or when the entire compositor should be enabled/disabled. Context for optimal use is absent.

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