get_semantic_scholar_author_papers

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core action ('List') and filtering option, but does not mention pagination behavior, field selection, ID format, or any requirements/constraints. This leaves significant behavioral ambiguity.

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 with no unnecessary words. It conveys the core action and the optional filter 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?

Despite having an output schema, the description under-specifies a tool with five parameters, no annotations, and no schema descriptions. It does not explain how to obtain author_id, what fields can be requested, or how pagination works, making it minimally viable only for the simplest invocation.

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?

The schema has 0% description coverage, so the description must compensate by explaining parameters. It only hints at publication_date_or_year via 'optionally filtering by publication date/year', but says nothing about author_id, limit, offset, or fields. This is insufficient for a 5-parameter tool.

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 uses a specific verb ('List') and resource ('an author's papers'), clearly distinguishing it from sibling tools like get_semantic_scholar_author_details or search_semantic_scholar_papers. It also notes the optional filtering by publication date/year, adding useful scope.

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 gives clear context: use this tool when you need to enumerate an author's papers, optionally filtered by date. However, it does not explicitly mention when not to use it or name alternative tools for related tasks, so it lacks explicit exclusions.

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