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

Goes well beyond the readOnly/idempotent annotations: discloses the 100-paper cap with no pagination, the 6-in-10 abstract coverage, the Personal+ account requirement, and the x402 pay-per-call price tiers with the exact _meta key. Only minor gap is not saying what an empty result or missing abstractions look like in the response.

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 usage, then pricing and quotas. Every sentence carries information, though the payment-scheme details make the tail dense and slightly harder to scan.

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 usefully enumerates return fields and documents access, cost and result caps. Nearly complete; the unexplained subject_type enum is the only substantive omission for a 4-param tool.

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%, and the description compensates for limit (cap of 100) and subject_id (must be resolved via search_subjects) plus elaborates sort semantics. However, it never explains the subject_type enum values keyword vs sector, which is the most ambiguous required parameter.

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 and resource ('top papers for one research topic') and enumerates the returned fields (title, DOI, venue, year, citations). It also distinguishes itself from sibling get_subject_ri by framing the choice as 'what to READ about a specific topic, rather than how active it is.'

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 says to resolve the topic with search_subjects first, and gives a clear when-to-use rule contrasted against the activity-oriented sibling. The sort options are also each tied to an intent (recent well-cited, classics, latest).

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