get_job_status

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

Describes that it queries the server, requires it to be running, returns specific fields (running, pending, done booleans, plus optional status_str, error, execution_stats). No annotations provided, but description fully covers behavioral expectations.

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?

Four sentences, front-loaded with purpose, no redundant information. Every sentence adds value.

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?

Provides purpose, inputs, outputs, prerequisites, and sibling guidance. No output schema, but return fields are described sufficiently.

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?

Only one parameter (prompt_id) with 100% schema coverage. Schema already says 'The prompt ID returned by enqueue_workflow'. Description repeats this but does not add new semantics beyond confirmation.

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 checks the status of ONE ComfyUI job by prompt_id. Distinguishes from sibling tools get_queue (whole queue) and get_history (full output filenames).

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 says when to use (check status of one job), when not (use get_queue for whole queue, get_history for filenames), and prerequisite (server running).

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