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

No annotations are supplied, so the description carries the full burden and does reasonably well: it discloses source set, that results are merged, deduplicated and ranked, what fields come back, and a concrete price of $0.003 USDC. It does not mention rate limits, failure modes, or payment/auth mechanics, which leaves a real gap for a paid tool.

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?

Three short sentences, front-loaded with purpose, followed by the scope exclusion and the call signature with cost. Every clause carries information; nothing is redundant.

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 and no annotations, the description usefully describes the return fields (snippets, authors, dates, DOIs, citations) and the pricing model, which is enough to call the tool competently. The omission of the lang parameter and of source-value syntax is the only meaningful gap.

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 description must compensate, and it only partly does. It names q as required and sources/limit as optional but gives no format, delimiter, valid source names, or default for limit (which is oddly typed as a string), and the lang parameter is never mentioned at all.

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+resource ('research search over open sources') and enumerates the backends (Wikipedia, OpenAlex, arXiv, Crossref) plus the merge/dedup/rank behavior. The clause 'Not a general web index' explicitly separates it from a generic web search, and its academic-source scope distinguishes it from siblings like read_url, extract_links, and company_research.

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?

'Use this for cheap research search over open sources' plus 'Not a general web index' gives a clear when-to-use and an implicit when-not. It stops short of naming a concrete alternative for the excluded case (e.g., use read_url for a specific page), so the routing is clear but not fully explicit.

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