search_papers_s2_tool

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

Discloses the 1 req/second rate limit and slowness, which is useful. No annotations, so description carries the burden; but lacks details on output behavior beyond what output schema provides.

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?

Short and front-loaded with key information. Every sentence adds value, but could be more structured.

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 output schema present, return values are covered. However, parameter semantics are missing. Adequate for a simple search tool but leaves gaps.

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 has no descriptions (0% coverage). Description does not explain 'limit' or 'query' parameters, adds no meaning beyond names.

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?

Clearly states the tool searches papers using Semantic Scholar, but does not distinguish from sibling tool 'search_papers_tool' which likely uses a different source.

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?

Mentions relevance sorting, TLDRs, and rate limit, implying when to use, but lacks explicit guidance on when to prefer over alternatives like OpenAlex or Scopus.

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