get_task

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

With no annotations, the description carries the full burden. 'Fetch' implies a non-mutating read, and 'current status and latest result payload' usefully signals idempotent polling and that results may supersede earlier ones. However, it says nothing about terminal states, behavior when the task is unknown/pending, auth, or rate limiting.

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 that states the action, the resource, and the two things returned, with no filler.

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 two-parameter tool with no output schema and no annotations, the description does mention what comes back (status and result payload), which partly substitutes for the missing output schema. It still omits polling/terminal-state behavior and error handling, leaving noticeable gaps.

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 both task_id and the action enum documented in the schema itself. The description adds only the 'flux-2' qualifier and no format, correlation, or enum guidance, so baseline 3 is appropriate.

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 gives a specific verb ('Fetch') and resource ('current status and latest result payload for a flux-2 task'), so an agent knows exactly what it retrieves. It does not explicitly contrast itself with siblings like remix_image or text_to_image, but the polling framing makes its role distinguishable.

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 explicit when-to-use guidance, no mention that this is a polling call to be repeated until the task reaches a terminal state, and no reference to the creating siblings (remix_image/text_to_image). The agent must infer usage context entirely.

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