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

No annotations are provided, so the description must fully disclose behavior, but it only states the output criterion ('most-cited recent papers') without explaining limitations, default behavior when no parameters are supplied, data source, or pagination. The 'Great for literature reviews' note is usage context, not behavioral transparency. This leaves significant ambiguity for an agent.

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 only two short sentences and is front-loaded with the primary function in the first sentence. Every word is relevant, with no fluff or repetition of the tool name.

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 list tool with no output schema and no annotations, the description provides a baseline level of understanding—what the tool returns and a key use case. However, it omits details about optional parameters, default behavior, and result format, which are important for correct invocation. It is adequate but not complete.

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 input schema has only 50% description coverage: 'years' is exemplified with '2024-2026,' but 'topic' has no description. The description adds the term 'domain' which maps to 'topic,' but it does not clarify acceptable formats, whether parameters are optional, or how 'years' is interpreted beyond the example. The description fails to fully compensate for the schema gap.

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 identifies the tool's purpose as returning 'Most-cited recent papers in a domain,' which is a specific resource and filtering criterion. It distinguishes itself from sibling tools like paper_recommendations or citation_graph by emphasizing recency and citation count, though it lacks an explicit verb like 'list' or 'search.' Overall, the intent is unambiguous.

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 phrase 'Great for literature reviews' provides a clear use case and implies when an agent would choose this tool. However, it does not explicitly mention when not to use it or name alternatives such as search_papers or paper_recommendations, so it stops short of full usage guidance.

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