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

No annotations are provided, so the description carries the full behavioral burden. It does disclose what comes back (title, authors, journal, year, DOI, citation count, abstract) and the ordering options, which is real added value; however it says nothing about result caps, pagination, rate limits, or whether a query requires/forbids special syntax.

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?

Two dense sentences with zero filler, front-loaded with the capability and source, followed by the field list and sort modes. Every clause carries information an agent can use.

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 shape need not be described. But with no annotations and zero parameter coverage, the definition should still cover q syntax and limit bounds — the two things most likely to cause a malformed or over-broad call.

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 0%, so the description must compensate. It does explain the sort dimension ('by relevance, date or citations'), which is critical because sort has no enum or description in the schema, but it leaves 'limit' unbounded (no max) and gives no guidance on q syntax (boolean operators, field queries).

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?

Specific verb+resource ('Search published research papers and articles') with explicit source (Crossref), returned fields, and sort modes. It implicitly distinguishes itself from arxiv_search via 'published'/(Crossref), but never names that sibling, so an agent must infer the boundary rather than being told.

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?

'Use to find and cite sources' gives a usage intent but no when-not conditions and no named alternatives. With arxiv_search, sec_full_text_search and book_search among siblings, the description could have routed the agent explicitly instead of implying it.

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