configure_manager

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

Discloses how actions are executed (HTTP API vs config.ini write) and that config.ini actions require restart. No annotations exist, so the description carries the full burden. Could mention if actions are reversible or error behavior, but sufficient for a config tool.

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?

Two sentences, front-loaded with purpose, no redundant information. Efficient and clear.

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?

Covers the main use cases and key behavioral differences. Lacks information about return values or success/error reporting, but given no output schema and tool simplicity, it is mostly complete.

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?

Adds context beyond the schema: explains the action split (live vs restart needed), notes value optional for reset_queue, and provides rationale for the fallback actions. Schema coverage is 100%, but description adds meaningful guidance.

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?

Clearly states it configures ComfyUI-Manager settings, mirroring comfy-cli manager commands. Distinct from sibling tools that deal with workflows, nodes, etc.

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?

Describes two categories of actions (HTTP API vs config.ini), noting that config.ini actions require a local ComfyUI path and a restart. Does not explicitly exclude scenarios or mention alternatives, but the context is clear.

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