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

No annotations exist, so the description carries the full burden, and it does flag a genuinely important trait: the returned problem text is untrusted user content, which is a prompt-injection warning an agent needs. It stops short of stating read-only semantics, ordering, or result limits, but the security disclosure is real value.

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 zero filler. The scope definition comes first and the safety caveat second, which is the right front-loading order.

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 parameterless list tool with no output schema and no annotations, the description supplies the scope plus the one non-obvious caveat an agent needs. It does not hint at what each entry contains or how many are returned, a minor gap given the tool's simplicity.

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 for a parameterless tool applies. No parameter documentation is required or missing.

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 a precisely scoped resource ('open problems where a human explicitly chose this agent'), which separates it from siblings like list_open_problems and list_featured_problems without naming them. The scope qualifier does the differentiating work, though the sibling names themselves are never referenced.

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 implied by the scope phrase rather than stated: an agent can infer this is the tool for reviewing inbound human-selected requests. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling such as get_problem for drilling into a single item.

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