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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and external-reach behavior are covered structurally. The description adds only marginally by implying citations are returned; it says nothing about result volume defaults, pagination exhaustion, or ranking behavior beyond what the schema already encodes.

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 short sentences with the capability first and the routing constraint second. No filler, no repetition of the title.

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?

With six parameters fully described in schema and annotations covering safety, the description supplies the only missing piece an agent needs: what domain of content this searches and where to go instead. No output schema exists, but 'citation details' gives a rough return-content signal; a note on result volume or pagination would make it complete.

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 every parameter (year_from/year_to, language, results, page) is already documented with ranges and an enum. The description adds no syntax or formatting guidance beyond restating 'Required: query', which the schema's required array already declares. 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?

States a specific verb+resource ('Find scholarly publications and citation details') and scopes it to 'by topic', which is enough to distinguish it from generic web search. It also names the sibling it is not (google_search), so an agent can route with confidence.

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 gives the exclusion and the alternative: 'Not general pages (use google_search)'. Combined with the required-parameter callout, the when/when-not pair is unambiguous.

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