get_execution_status

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 discloses the environment prerequisite (COMFYUI_HOST) and the shape of returned data, which helps, but says nothing about behavior when the prompt is unknown, whether it waits or is instantaneous, or error conditions.

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?

Three short sentences, front-loaded with the core action and return contents, with the env requirement last. No filler, though the prerequisite sentence could be tied more tightly to invocation.

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 one-parameter read tool with no output schema, the description adequately covers what comes back and the environment requirement. Missing only failure/empty-result handling, which is a minor gap at this complexity.

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 coverage is 100% and the single parameter's meaning ('Prompt id returned by execute_workflow') is fully documented in the schema. The description adds no syntax or provenance detail beyond that, so baseline 3 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?

States a specific verb and resource ('Get execution status and outputs for a prompt') and enumerates the return payload (status, image filenames, view URLs). It does not explicitly distinguish itself from close siblings like get_execution_progress or get_last_output, so it stops short of a 5.

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?

Usage context is only implied: the prompt_id parameter ties it to a prior execute_workflow call, and it notes the COMFYUI_HOST prerequisite. There is no explicit statement of when to prefer this over get_execution_progress, get_last_output, or get_history.

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