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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description goes further by disclosing the pagination contract (next_cursor, truncated flag), the presence of retraction integrity flags, and a data-trust warning that title/authors/venue/abstract and open_access links are untrusted third-party data — genuinely useful context an agent cannot get from annotations.

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 purpose, then return shape, then pagination, then filter discipline. No sentence is padding; even the closing trust warning carries actionable information, and the length is proportionate to a 16-parameter search tool.

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?

An output schema exists, so return values need not be explained, yet the description still summarizes them usefully. With 100% schema coverage, pagination behavior, filter-selection policy and data-trust caveats all present, an agent has everything needed to call this correctly without opening 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 100%, so the schema already documents all 16 parameters and the baseline is 3. The description adds a cross-cutting semantic rule the schema does not state — every filter is optional and should be set only on explicit user request — which materially changes how the filters should be populated rather than merely restating them.

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 verb and resource ('search scholarly literature with one plain-language query') and enumerates what comes back: ranked hits with ids, title, authors, year, venue, citations, abstract, retraction flags and open-access links. That is far beyond restating the name. It stops short of 5 because the single sibling, expand_citations, is never referenced, so the agent gets no explicit in-text differentiation.

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 concrete usage rules: one plain-language query per call, call again with a new query for another angle, page with next_cursor when 'truncated is true', and the strong filter discipline 'set one ONLY when the user explicitly asks for it.' That is clear context and near-explicit when/when-not guidance; only the absence of any mention of the alternative tool keeps it from a 5.

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