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

With annotations only declaring readOnlyHint and openWorldHint, the description carries real behavioral weight: the $0.05 x402 charge, the pre-payment check, the free 'not_covered' 404 failure mode, and the licensing rule (abstracts only for CC0/PD/CC BY/CC BY-SA, metadata+link otherwise). These are non-obvious traits the agent could not infer from structured fields.

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 core purpose is front-loaded in the first clause, and the follow-on clauses all carry information (licensing behavior, pricing, failure mode) rather than filler. The single run-on paragraph packed with semicolons is dense but not wasteful.

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?

There is no output schema, but the description still specifies the return shape (authors, year, venue, DOI, citations, conditional abstracts, numbered synthesis citations), the cost, and the failure case. For a paid, no-output-schema tool, nothing essential is missing.

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 100%, so the schema already documents query, year_from, max_papers, synthesize, and include_live. The description adds narrative context for synthesize ('cites the papers as [n]') and include_live ('filled with a live search... when the archive has fewer papers'), but adds no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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 states a specific verb+resource ('Research brief on any topic') and enumerates exactly what the brief contains: archive papers plus live search, per-paper metadata, and an AI synthesis. It is clearly distinguishable from siblings like search_archive, search_specs, and get_fulltext, which return raw results rather than a synthesized brief.

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 implies the use case ('one call') and describes the fallback condition (free 404 if nothing is found anywhere) and the payment trigger, but never states when to prefer this over search_archive or get_fulltext, which are the obvious alternatives. Usage is inferable rather than explicit.

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