comfy_cli_status

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

Discloses underlying commands (`comfy which`, `comfy env`) and JSON contract, but lacks details on side effects, auth requirements, or rate limits. No annotations present.

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 filler. Every sentence earns its place.

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?

Adequate for a simple inspection tool, but lacks details about output format, error handling, or parameter behavior beyond what the schema provides.

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 description partially maps to the `detail` enum by mentioning two of four values, but doesn't explain each enum option or the `workspace` parameter beyond the schema. Schema coverage is 50%, so description adds limited value.

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 tool inspects the comfy-cli integration and ComfyUI environment, distinguishing it from sibling tools focused on jobs, models, or workflows.

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?

Explicitly advises calling before local CLI operations when workspace or server routing is uncertain, providing clear usage context. Does not mention when not to use or alternatives.

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