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

With no annotations provided, the description carries the full behavioral burden and mostly succeeds: it discloses JSON-only output, a hard cap of 3 papers, no payment, and the important caveat that it does not claim a paper proves a statement. It doesn't cover rate limits or failure behavior, but the key behavioral traits are transparent.

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 compact and front-loaded, but it contains a direct contradiction between '3-10 scholarly candidates' and 'Returns at most 3 papers.' It also repeats the free/no-payment idea twice, which slightly reduces the clarity and efficiency of the text.

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 six-parameter tool with no output schema, the description covers the main return fields and an important epistemic caveat, which is useful. However, it omits parameter semantics and leaves the candidate-count inconsistency unresolved, so an agent may misjudge result limits and available filters.

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 description coverage is only 50%, and the description adds little parameter meaning beyond the schema. It does not explain to_year, from_year, or open_access_only, nor does it clarify defaults or interactions with fields. The query parameter is the only one implicitly supported by the description.

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 uses a specific verb ('Find') and identifies the resource ('scholarly candidates'), and it lists the key returned identifiers and metadata. The free-preview framing also distinguishes it from the paid evidence_pack sibling. However, the result count is internally inconsistent ('3-10 scholarly candidates' vs 'Returns at most 3 papers'), which blurs the scope.

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 'Free preview' and 'no payment' phrasing implies this is a limited no-cost alternative to the full evidence_pack tool, but it never explicitly states when to choose this tool over evidence_pack or the citation_report siblings. Usage context is present but only by implication.

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