clo_ui_nest_all_fabrics

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

With no annotations, the description carries the full burden, and it does disclose important behavior: it uses Windows UI Automation, it cannot change CLO's mode menu, and it returns the marker it produced. It does not describe failure behavior if CLO is not in the required mode, but the core action, prerequisite, and output are clearly stated.

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 compact and front-loaded: it names the exact action first, then gives the use case, prerequisite, and return value. Every sentence adds necessary context and there is no filler.

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 zero-parameter, no-output-schema tool, the description covers the use case, mode prerequisite, and return value. It is slightly incomplete because it does not state what happens if CLO is not in Printing Layout mode or if the print layout is not empty, but overall an agent has enough to select and call 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 tool accepts zero parameters, and the schema's empty properties object fully captures that. There is no parameter detail for the description to add, so the baseline score applies.

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 states a concrete UI automation action ('Click Nest All Fabrics'), the target editor (Print Layout Editor), and the specific purpose (enabling API nesting to work). This clearly differentiates it from sibling nesting tools like nest_patterns by describing the UI fallback mechanism.

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?

It explicitly identifies the situation where this tool should be used ('for when the print layout is empty') and explains why it is necessary before API nesting can work. It also states the prerequisite that CLO must be in Printing Layout mode and notes that the mode menu cannot be driven through UI automation.

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