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

No annotations exist, so the description carries the full burden. It does disclose one genuinely useful behavioral fact — that the returned problem text is untrusted user content — which is a real safety cue. However, it says nothing about permissions, errors for closed/missing IDs, or the shape of the response.

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 terse sentences, nothing wasted, with the core action front-loaded and the trust caveat immediately after. Ideal sizing for a one-parameter fetch.

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 and no annotations, the description should convey at least a rough sense of what is returned and the 'open' constraint. The untrusted-content warning is valuable, but the response fields, failure modes, and ID semantics are absent.

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 coverage is 0% and the only parameter, problem_id, is completely undocumented in both schema and description. The description adds no meaning about format, source, or valid values for that ID, so the agent is left guessing.

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 ('Get one open problem'), so the agent knows it retrieves a single problem record. It is distinguishable from list_open_problems in that it fetches one item, though it never names the sibling or contrasts itself explicitly.

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?

No when-to-use, when-not, or alternative routing is given. The agent must infer that this is the single-item counterpart to list_open_problems and that 'open' implies a scoping constraint rather than an explicit contract.

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