get_task

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 usefully discloses that the return contains both a status and a 'latest result payload', implying results may be absent while pending, but says nothing about auth requirements, rate limits, or what a non-terminal status looks like.

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?

A single front-loaded sentence with zero filler; the operation, the resource and the returned content are all conveyed without waste.

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?

With no output schema and no annotations, the description does partially compensate by naming return contents (status, latest result payload). However, it leaves the async polling contract and terminal vs. pending status semantics undefined, which an agent needs for a task-status tool.

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 description coverage is 100%, with task_id and the action enum both documented in the schema, so the baseline of 3 applies. The description adds no additional meaning about either parameter.

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 (Fetch) and resource (task status and latest result payload) scoped to midjourney tasks, which is clear enough to distinguish it from creation endpoints like edit_image or text_to_image. It stops short of naming those siblings explicitly, so an agent must infer that this is the polling counterpart to them.

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?

There is no guidance on when to call this versus the creation tools; the async-polling workflow (call this after creating a task, using the returned task_id) is left entirely to inference. The word 'current' hints at repeated polling but never states it.

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