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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds a useful behavioral caveat that matching is heuristic rather than semantic equivalence, but it does not describe result quality, ranking, limits, or what the returned matches look like.

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?

The description is a single compact sentence that front-loads the core purpose and appends the most important caveat. There is no wasted wording.

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 one-parameter read-only tool, the description covers the core intent and a key caveat about matching quality. However, without an output schema it should say more about what the tool returns or how matches are ranked, and the parameter remains underspecified.

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%, so the schema provides only the property name 'question' with no further detail. The description implies that the input is the question to match, but it does not explain formatting expectations or how the input is compared against open research questions.

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?

The description states a specific verb and resource: finding open research questions that may be related. This is clear enough for an agent to know what the tool does, but it does not explicitly distinguish it from siblings such as research_questions or knowledge_search.

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?

The description implies a matching use case but gives no explicit guidance on when to use this tool instead of alternatives like research_questions or knowledge_search. There is no mention of prerequisites, exclusions, or sibling tools.

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