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

No annotations are provided, so the description carries the full burden, yet it discloses almost nothing behavioral: no pagination, no default limit, no ordering guarantees, no auth requirements, no return shape beyond a field list. The parenthetical 'abstract, status, reads, rating' is the only signal about output, which is weak for a read tool with zero annotation coverage.

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?

It is short, but it is under-specified fragments joined by semicolons rather than front-loaded prose. There is no wasted word, yet the terseness sacrifices clarity — this reads as note-taking, not a usable definition.

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 6-parameter filter tool with no annotations, no output schema, and 17% schema coverage, the description is far too thin. It should carry the load on filtering semantics, defaults, and return fields, but only gestures at a field list and four sort keywords.

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 only 17% (just 'format'), so the description must compensate — and it largely does not. It restates the sort enum values ('new, hot, top, open') without explaining their meaning and says nothing about ptype, topic, status, or limit. The filter parameters that define this tool are undocumented in both places.

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 name gives a clear verb+resource (list_papers), and the fragment 'Papers (abstract, status, reads, rating)' hints at a listing tool that returns those fields. However, the description itself never states a verb or that it lists papers, and it draws no boundary against siblings like get_paper, read_paper, or search. The purpose is only inferable by combining name and fragment.

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 when-to-use guidance, no mention of alternatives, and no prerequisites. It is not even clear how this differs from get_paper/read_paper/search, leaving the agent to guess. The sort values are listed but not framed as usage conditions.

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