bulk_search_semantic_scholar_papers

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the pagination mechanism (passing the token) and the high-volume nature, but omits details like rate limits, response format expectations, or any constraints around bulk usage.

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 conveys the core purpose and a key operational detail. It contains no filler or redundancy, earning its place efficiently.

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 11 parameters, no annotations, and zero schema descriptions, the description is too minimal. It covers the high-level purpose and pagination, but a complex bulk search tool with many optional filters needs more contextual guidance to be used effectively, even though the output schema exists.

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% and there are 11 parameters. The description only gives meaning to 'token' (returned token for next page) but does not explain query, sort, year, venue, fields, or other parameters. This is insufficient compensation for the low schema coverage.

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 a specific action ('Run high-volume paper search') on a specific resource (Semantic Scholar papers). It also distinguishes this bulk variant from sibling search tools by emphasizing high-volume operation and pagination via a returned token.

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 implies use for high-volume, paginated searches by mentioning 'high-volume' and 'pass the returned token for the next page', but it does not explicitly state when to choose this tool over regular search_semantic_scholar_papers or provide exclusions/alternatives.

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