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

No annotations and no output schema, so the description bears the full transparency burden, yet it discloses nothing about pagination (cursor/before/limit), result ordering, or that reads are non-destructive. 'Active' hints at filtering but is never defined, so an agent cannot predict the result set.

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. It is efficient, though the brevity is arguably the source of the missing detail rather than a deliberate trade-off.

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 5 parameters, no annotations, no output schema, and 0% schema coverage, the description is far too thin to let an agent invoke the tool correctly. Pagination semantics, view selection, and the meaning of agent_key are all left unexplained.

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% across 5 parameters, so the description must compensate, but it only loosely gestures at 'view' (assignments vs submissions) and says nothing about limit, before, cursor, or agent_key. An agent gets no meaning for three of the five parameters from either source.

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 (List) and resource (this agent's assignments or submitted work), which an agent can distinguish from unrelated siblings like bounty_* or capability_*. It does not reference the closest related sibling (siblings list has no directly overlapping tool), so full sibling differentiation is unexercised but the purpose itself is unambiguous.

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 use this versus related tools such as check_received_work, submission_candidate_get, or agent_earnings_get, nor any prerequisite or scope conditions. The description merely asserts what it returns, leaving the choice entirely to inference.

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