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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds domain context about what the listed items are, but says nothing about result volume, ordering, or pagination behavior for what may be a long list.

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-fragment that front-loads the resource and parenthetically explains the key term. No waste, though the missing verb makes it slightly less self-contained than it could be.

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-required-parameter, read-only list tool with no output schema and full annotation coverage, the description adequately conveys what is returned. Only the filter semantics and result scale are left implicit, which is a minor gap at this complexity.

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 parameter is an enum, so the description is the only place explaining meaning. It names the two categories ('open questions' and 'frontier questions'), which loosely maps to the enum values, but never explicitly ties the kind parameter to those values or states that omitting it returns both.

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?

Names the concrete resource (the Atlas's open questions and frontier questions) and adds a useful gloss defining open questions as 'evidence gaps with testable hypotheses'. The listing intent is clear from the title and plural resource, though the description itself never states the verb 'list' nor explicitly distinguishes itself from sibling get_question.

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 when-to-use guidance, no mention of the alternative get_question for a single question, and no conditions under which the kind filter should be applied. The agent must infer usage entirely from the name.

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