Unified Research Context

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

No annotations are provided, so the description carries the full burden. It discloses several meaningful behaviors: it prunes tools to prevent API waste, sanitizes snippets against prompt injection, reranks on CPU, and returns bounded context. This is strong transparency, though it stops short of covering all operational details such as required auth or external API calls.

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 compact and front-loaded with a clear pipeline label, followed by a numbered list that makes each behavior easy to scan. Every line adds some information, though the phrasing is somewhat jargon-heavy and could be tightened.

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?

An output schema exists, so the return type does not need to be explained in detail. The description covers the main invocation-relevant behaviors: tool selection, pruning, sanitization, reranking, and bounded output. It is incomplete only in that it does not specify what a valid `query` looks like or how this tool relates to sibling matching tools.

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%, so the description must compensate. It indirectly clarifies `top_k` by saying it selects the 'top 1-2 optimal tools' and clarifies `query` by mentioning 'semantic capability match.' However, neither parameter is explicitly defined, and the relationship between `top_k` and the stated 'top 1-2' boundary is left ambiguous.

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?

Describes a specific multi-source research context pipeline and states the outcome: 'returns bounded, dense grounded context.' The numbered behaviors make the tool's role clear, though it does not explicitly contrast itself with the sibling match_tools_for_query, which appears closely related.

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 explicit guidance on when to use this tool versus alternatives such as search_academic_papers, fetch_paper_deep_context, or match_tools_for_query. The description implies it is useful for multi-source context gathering with tool selection, but it does not state conditions, exclusions, or when a sibling would be more appropriate.

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