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

With no annotations, the description carries the full burden and delivers: Personal+ account requirement, a hard 100-paper cap with no pagination, ~60% abstract coverage, and a detailed pay-per-call pricing model including the x402 payment field. This is unusually rich operational context.

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 purpose and routing before behavior and pricing, and nearly every sentence earns its place. The pricing sentence is long and dense but delivers information an agent needs before calling.

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?

No output schema exists, so the description usefully lists return fields and abstract coverage, plus auth and cost. The main residual gap is the unresolved semantics of subject_type/subject_id, which are neither described here nor in the schema.

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 coverage is only 25%, so the description must compensate. It explains the sort modes well (though the schema already documents sort) and mentions the 100 cap implied by limit, but says nothing about what subject_type values ('keyword' vs 'sector') mean or the subject_id format, leaving half the parameters semantically thin.

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?

States a specific verb+resource ('the top papers for one research topic') and enumerates the returned fields (title, DOI, venue, year, citations), which separates it from the sibling ranking tools get_subject_ri and get_subject_history.

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?

Explicitly routes usage: 'Use it when asked what to READ about a specific topic, rather than how active it is,' contrasting with the activity-oriented siblings. It also names the prerequisite (resolve the topic with search_subjects first) and explains when to pick each sort mode.

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