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

Discloses a non-obvious transport quirk (POST but parameters in the query string, JSON body rejected), the exact return shape (id plus results[] with title/link/snippet only), approximate latency and payload size, and the absence of page text. Annotations declare destructiveHint=true and readOnlyHint=false, and the description is consistent with a network-calling search rather than contradicting them.

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 action and the transport warning, and the routing hint to post_tavily_search lands early. A few sentences are stylistic filler ("Its virtue is how little it returns") and the pricing comment block adds noise, so it is efficient but not waste-free.

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, yet the description still pins down the practical contract: transport method, required query, result fields, the returned id and its downstream use, cost, and expected latency. Nothing an agent needs in order to invoke and chain this call correctly is left implicit.

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, but the description adds genuinely useful calling-convention detail: the parameters must go in the query string, a body is not accepted, and it restates the default (10) and ceiling (100) in prose. That is meaningfully beyond the schema's field-level descriptions.

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 and resource ("Search the open web and get back a lean result list") and characterizes the output shape, so the agent knows this is a lightweight web search rather than a content-fetching tool. It does not differentiate itself from the similarly-named siblings post_scholar_search_scholar and post_scholar_search_mixed, which an agent would otherwise confuse it with.

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?

Gives a clear selection rule: use this when you only need to know what exists, and use post_tavily_search when you need page content, plus a follow-up hook (keep the id for post_scholar_search_explain). It stops short of explicit when-not guidance against the other scholar search variants listed as siblings.

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