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

No annotations are present, so the description carries the full burden. It mentions AI-ranked relevance and the underlying API, but lacks details on authentication, rate limits, or idempotency. While it implies a read-only search, it does not explicitly state safety or behavior.

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, information-dense sentence that covers the scope, scale, and API. It is concise, but could be slightly more structured with line breaks or bullet points for clarity.

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?

The tool lacks an output schema, yet the description does not explain what fields or information will be returned (e.g., title, authors, abstract). Given the complexity and sibling tools, more context on return value and unique features is needed.

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 100%, with parameters query and limit described. The description does not add extra meaning beyond the schema; it repeats the notion of searching but provides no advanced query syntax or usage tips.

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 tool searches over 226M+ academic papers across all fields using the Semantic Scholar Graph API with AI-ranked relevance. It is very specific about the resource and functionality.

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 guidance on when to use this tool versus alternatives like search_arxiv, search_openalex, or search_pubmed. The description only states it covers all fields but does not provide exclusion criteria or context for selection.

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