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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: the 50-entry page size, the 10,000-match reachability ceiling, and the fact that entries are INSPIRE's verbatim text with abbreviated long author lists. Only minor gaps remain (e.g., no note on output shape beyond the existing output schema).

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 core action and output formats, then usage modes, then pagination caveats. Dense but every sentence carries information; slightly long, with the author-abbreviation note being a nice-to-have rather than essential.

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 restated. Combined with the pagination ceiling, format options, and query routing, the description gives an agent everything needed to invoke the tool correctly against its complex query semantics.

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 baseline is 3. The description still adds value by explaining how the query parameter maps to use cases (named papers vs. topic/author/citing set) and what the format options produce ('\bibitem entries in European or US style'), which goes beyond the schema's terse enum labels.

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 (export INSPIRE-HEP citation entries for papers a query selects) and the output forms (BibTeX / LaTeX \bibitem, EU or US style). It is clearly distinguishable from siblings like get_citation_summary or search_literature, which retrieve or search rather than emit formatted bibliography entries.

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 covers the two main usage modes: naming specific papers via recid/arxiv/doi, or exporting a topic, author, or citing set using any query cern_inspire_search_literature accepts. It also routes the agent to cern_inspire_list_reference topic search_syntax for query grammar, which is exactly the alternative-selection guidance needed.

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