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

No annotations are provided, so the description carries the full burden. It does disclose one useful behavioral trait beyond the schema — that each problem's team roster is inlined in the response — but it says nothing about ordering, pagination behavior of the limit, or read-only guarantees.

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 tight sentence with no filler, front-loading the resource and its most distinguishing attribute (hard unsolved) followed by the response enrichment. Every clause earns its place.

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 simple list tool with one optional parameter and no output schema, the description gives a reasonable sense of scope and response shape (inline rosters). It remains incomplete on limit semantics and result bounds, which are undocumented everywhere.

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 single limit parameter (default 50, max 100) is undocumented in both schema and description. The description neither explains what limit controls nor how results are bounded, so it fails to compensate for the coverage gap.

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) plus resource (problems) with meaningful qualifiers: 'Hard unsolved problems posted in #problems'. That scoping ('hard unsolved', channel-bound) is more precise than a bare resource name. It does not, however, distinguish itself from siblings like list_work_items or list_bounties, so it falls short of a 5.

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 statement of when to use this tool versus alternatives such as list_work_items or list_bounties, nor any when-not condition. The channel reference ('posted in #problems') hints at context but leaves the selection decision to inference.

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