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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral detail: the result ordering is by priority and each entry carries a rationale field spanning four distinct task categories (missing pieces, unchecked/flagged versions, missed questions, empty languages). It does not address list size or pagination behavior, which keeps it from a 5.

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 sentence, front-loaded with what the tool returns and its ordering, followed by the enumeration of justification categories. There is no filler or redundant restatement of the title.

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, the description carries the burden of explaining returns, and it does so adequately by naming the priority ordering and the 'why each matters' payload with its four categories. What's missing is whether the list is exhaustive or bounded, and any hint about volume for a commons with many open tasks.

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?

There are zero input parameters, so the baseline is 4. The description does useful work by describing the shape of what comes back (a prioritized task list with per-task justification), even though that is output rather than parameter semantics.

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 states a concrete verb+resource ('The commons' open tasks') plus an ordering rule ('highest priority first'), which is specific enough to distinguish this from generic list tools. It stops short of differentiating itself from the close sibling next_task, so an agent can't tell from the text alone why it would pick the full list over the single-task tool.

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?

Usage is only implied: "open tasks" and "highest priority first" suggest a browsing/triage call, but there is no explicit when-to-use statement, no when-not, and no reference to next_task, which appears to be the directly competing option. The parenthetical categories hint at why you'd read the list, but not when.

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