get_job_status

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

With no annotations, the description carries the full burden. It correctly implies a read operation, but does not disclose potential errors, rate limits, or whether it is idempotent. Basic transparency is provided but not comprehensive.

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 a single sentence of 11 words, no filler, and immediately states purpose. Excellent conciseness with no wasted text.

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?

The tool is simple with one parameter, but no output schema exists and the description does not explain what the status response includes. For a status-checking tool, knowing possible return values (e.g., pending, completed, failed) is important. The description is adequate but incomplete.

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%, so the description is not expected to add much. It does not repeat the param description but provides context that the prompt ID comes from 'enqueue_workflow'. This adds mild value, meeting the baseline for high coverage.

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 uses a clear verb ('Check') and specifies the resource ('execution status of a ComfyUI prompt/job'). It mentions the key input ('by its ID'), which distinguishes it from siblings like 'enqueue_workflow' and 'cancel_job'.

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 implies usage after enqueuing a workflow, but does not explicitly state when to use it versus alternatives, nor does it provide prerequisites or exclusions. No guidance on when not to use.

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