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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context: the sort order (newest first) and the shape of each item (venue, links, abstract). It stops short of saying whether the whole list is returned or truncated, which is the remaining gap.

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?

A single front-loaded sentence with zero filler; every clause (resource set, ordering, returned fields) carries information an agent can act on.

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?

For a simple two-optional-parameter read tool with rich annotations, the description is close to sufficient, but it omits result-set sizing/pagination and leaves the filtering parameters unaddressed. The preprint/enum mismatch slightly undercuts completeness.

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?

Only one of the two parameters has schema documentation (50% coverage), so the description should compensate but does not explain the `type` filter or how `year_from` interacts with it. Worse, the description lists 'preprints' as a category while the enum offers only paper, technical-disclosure, whitepaper and thesis, which can mislead an agent about valid values.

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 sentence enumerates the exact resource set (papers, preprints, technical disclosures, thesis, whitepaper) and states the ordering (newest first), which clearly separates it from siblings like list_posts, list_projects and list_results. The verb 'list' is only implied by the tool name rather than stated, which keeps it just short of a 5.

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 choose this over `search` or the other list_* tools, and no mention of whether the filters are optional or how to narrow results. The agent must infer usage from the name alone.

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