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

readOnlyHint=true already declares the safety profile, so the description's added value is limited to 'open public', which usefully signals that only publicly visible questions are returned. It says nothing about pagination behavior, ordering, result volume, or what happens when id is supplied versus omitted.

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 front-loaded sentence with zero filler, which is structurally sound. It is arguably too terse for a three-parameter tool, but nothing in it is wasted.

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, no parameter documentation, and no pagination or lookup-mode explanation, the agent cannot tell what a call returns or how to page through results. For a read-only listing tool this leaves real gaps, even though the safety profile is covered by annotations.

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% across three parameters (id, limit, cursor), and the description never mentions any of them. The phrase 'registry' faintly implies a paged listing, but neither the id-lookup mode nor the cursor-based pagination contract is stated anywhere.

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 ('Read') and resource ('open public research question registry'), which clearly separates it from the write-side sibling research_submit_question. It stops short of naming an alternative or clarifying how it differs from research_core or research_match, so it is clear but not fully differentiated.

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 guidance on when to use this versus research_core, research_match, knowledge_search, or research_submit_question. The only implied usage is 'read the registry', leaving the agent to infer whether this is a listing, lookup, or search entry point.

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