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

No annotations exist, so the description carries the full burden. It does disclose useful behavior: implicitly read-only summary output, list of returned metrics, that no inputs are required, and the cost ('[Free · 1 credit]'). It says nothing about permissions, result size limits, pagination, or how 'top years'/'top venues' are ranked or truncated — material gaps for a personal-data aggregation tool.

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?

Front-loaded with the resource and result contents, then the usage rule, then the cost tag — good ordering with no filler sentences. The capitalized 'AND' and bold-style emphasis on most_connected_papers is mildly noisy but serves to highlight a commonly requested metric.

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 no output schema, the description must describe returns, and it does so comprehensively by listing all metric groups. With zero parameters and no annotations, the remaining obligations are behavioral caveats (result limits, ranking definitions, auth scope), which are only partially addressed.

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 tool takes zero parameters, so the baseline is 4 by the rubric's own rule; the description does clarify that no node_id is needed, which is a small value-add over an empty schema. Since there are no parameters to explain, it earns the baseline rather than exceeding it.

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 names a specific resource (the requesting user's tracked-paper library) and enumerates exactly what is returned: total count, top years, top venues, recent titles, most-starred, and most_connected_papers. It explicitly distinguishes itself from graph/node siblings by stating 'Always library-scoped — no node_id inputs needed', so an agent can separate it from library_node_context or citation_graph without opening a schema.

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?

It gives a strong positive trigger — 'Use FIRST whenever the user asks anything about THEIR library size, distribution, recent additions, or graph connectivity' — and a clear scoping condition (no node_id). It does not name when-not cases or a specific alternative sibling for library-level questions that are not statistical summaries, which keeps it short of a 5.

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