get_agent_work

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read of pending work but says nothing about ordering, pagination, whether results are consumed/claimed by reading, what happens when no work exists, or what the response contains — all material for a work-queue tool.

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 no filler, so it is concise, but conciseness here tips into under-specification — the one clause leaves core questions (filtering, return shape, relationship to sibling tools) unanswered.

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, zero-coverage, annotation-free tool sitting among nineteen overlapping generation/queue siblings with no output schema, the description is far too thin. It does not compensate for any of those structural gaps, so an agent must guess at correct invocation.

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 0% and the description never mentions either parameter. "batch_id" is undocumented in both places, so an agent cannot know whether it narrows to a specific batch or is required for meaningful results; "limit" is likewise unaddressed with no default or max behavior explained.

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 names a verb ("Get") and a resource ("active-phase image generation, visual review or repair tasks") scoped to a specific agent, which is more than a tautology. However, "active-phase" is unexplained jargon and the tool is not distinguished from close siblings such as get_generation_status, get_queue_status, or get_batch_status, so an agent cannot easily tell which of these retrieves actual work items versus job state.

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 many state-inspection siblings, no prerequisites, and no stated exclusions. The description also omits any hint about the practical use case (e.g., polling for next work item after claiming a job), leaving usage entirely to inference.

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