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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds an unusual security note ('Assignment grants no wallet signing authority'), but the sentence is ambiguous -- it describes assignment rather than listing -- and says nothing about result scoping (current user vs. org), ordering, or whether completed tasks are included.

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?

Two short sentences with the primary purpose front-loaded, no filler or restated schema. The second sentence is somewhat tangential to a list operation, which keeps it just shy of a 5.

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 zero-param, annotation-rich, read-only listing tool with no output schema, the description covers what the tool returns at a high level (pending tasks and deadlines). Slightly more on the shape/scope of results would make it fully self-sufficient, but nothing critical is missing before invoking it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The schema also declares additionalProperties:false, making the absence of inputs unambiguous.

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+resource ('List your pending review tasks') plus the extra payload of deadlines, which lets an agent distinguish it from the mutation siblings accept_review_task/assign_review_task. It never explicitly contrasts itself with the read siblings such as get_card_bounty_review or get_managed_bounty_review, so differentiation is implied rather than stated.

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?

'Your pending review tasks' implies the caller should use this to see their work queue, so usage is inferable. However, there is no explicit when-to-use/when-not, no mention of how it relates to the many retrieve-one-review siblings, and no prerequisites stated.

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