get_comfy_log

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

No annotations are provided, so the description carries the full burden. It clearly states this reads the Python-side console, not the browser, and explains what kind of output it returns (import errors, tracebacks). It also discloses filtering behavior (level drops untagged output, search/regex). This is strong behavioral disclosure, though it stops short of describing the exact output format or side effects.

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 moderately sized but every sentence adds value. The opening paragraph establishes the tool's unique value, and the Args section is terse and unambiguous. No filler or redundancy.

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?

Given the tool's niche role, the description covers the core use case, differentiates from other tools, and explains all parameters. An output schema is present, so return structure details are not required. The context of sibling tools is addressed through the Python-vs-browser distinction.

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?

Schema descriptions are absent (0% coverage), but the description thoroughly explains all four parameters: lines, level, search, regex. It clarifies that level drops untagged output, and regex modifies search. This fully compensates for the schema's lack of 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 opens with 'Read ComfyUI's console - the Python side', giving a specific verb and resource. It clarifies this is the terminal, not the browser, differentiating it from the sibling get_console_log. The contrast with /object_info also helps distinguish its niche.

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 explains that import failures and tracebacks land here, and that nothing else in the server can see this data. This implies use when a node fails to load or when debugging dependency issues. It contrasts with /object_info but does not explicitly name the sibling get_console_log as the alternative, though the Python-vs-browser distinction makes the intended usage clear.

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