set_comfyui_setting

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

With no annotations provided, the description carries full burden. It discloses that changes persist immediately but take effect on next UI load, that values are stored as-is without coercion, and that unknown ids are stored but ignored. It also describes the return value structure.

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 relatively long but every sentence adds necessary information. It is front-loaded with the main action and structured logically. A slight reduction in wordiness could improve conciseness, but it remains effective.

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?

Despite no output schema, the description explains the return shape ({ id, previous, value }). It covers both required parameters with examples and nuances. The tool is simple (2 params), and the description provides sufficient context for correct invocation.

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 input schema already has 100% coverage with descriptions for both parameters. The description adds value by listing example known ids, specifying accepted value types for id, and clarifying type coercion behavior for values. This goes beyond the schema's basic descriptions.

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 it modifies a ComfyUI user's persisted frontend UI setting by id. It distinguishes between this and the related get_defaults/set_defaults tools, and provides specific known ids, making the purpose unambiguous.

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?

The description explicitly states when to use this tool (modify frontend settings), what not to confuse it with (get_defaults/set_defaults), and includes important usage notes about persistence, refresh behavior, and type coercion. It also explains the effect of unknown ids.

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