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

Annotations already establish the read-only/idempotent profile; the description adds the important query-string-not-body constraint and a performance estimate. It also points out that `number_of_citations` is unavailable from general web search, though the raw return shape is already present in the 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?

The description is dense but front-loaded with the core purpose and then proceeds logically through request format, return values, and usage guidance. Some extras such as 'Measured at under 2 seconds' are marginal, so it is not maximally lean.

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?

Covers the main invocation details, return highlights, and routing to related tools, and the output schema fills in the full response structure. It is slightly incomplete by not distinguishing from `post_scholar_search_web`, but overall the agent has what it needs to select and call this tool correctly.

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% and the description mostly restates parameter names and constraints already in the schema. It adds little beyond noting that parameters go in the query string, which is a transport detail rather than new semantic meaning for individual parameters.

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 opens with 'Search academic literature' and goes on to specify the distinguishing value (peer-reviewed sources, citation counts). It also names sibling tools for different cases, making the tool's purpose unmistakable.

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 says to use it when peer-reviewed sources or citation counts matter and names `post_tavily_search` for current events/product pages, plus `post_scholar_search_mixed` and `post_scholar_search_explain`. However, it does not address the closely named sibling `post_scholar_search_web`, so the routing guidance is slightly incomplete.

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