find_research_gaps

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'analyze,' which implies a non-destructive operation, but it doesn't explicitly state whether it modifies state, what side effects exist, or how it handles the papers (e.g., reading vs. fetching). This is minimal.

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, front-loaded sentence that communicates the core action and outcome without any wasted words. It's appropriately concise for a tool that might need more detail but doesn't have it.

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?

Given the tool has 2 parameters, no annotations, 0% schema coverage, and an output schema (whose content is unknown), the description is insufficient. It fails to tell the agent how to construct the 'papers' input, what the output will look like, or any constraints on the analysis. More context is needed for effective use.

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 description provides no explanation of the parameters. It doesn't clarify what 'topic' should be, how 'papers' should be structured (even though the schema allows any objects), or any required properties within those objects. The description completely fails to compensate for the lack of schema documentation.

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 clearly states the verb 'analyze' and the resource 'multiple papers' with the specific goal of identifying research gaps. This distinguishes it from siblings like compare_papers (comparison) and extract_limitations (limitations extraction), so an agent can tell them apart.

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 gives no guidance on when to use this tool versus alternatives. It doesn't mention any conditions or contrast with siblings, leaving the agent to infer when research-gap analysis is appropriate versus other paper-analysis tools.

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