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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that — no rate limits, result shape, or latency notes — so it neither adds value nor contradicts anything.

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 purpose in the first clause and no wasted preamble. The trailing examples sentence partially repeats the category list already named in the first sentence ('news, facts, prices, or events' vs 'recent news, stock prices, weather, product information'), which is mild redundancy.

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?

For a fully annotated, fully schema-documented search tool with no output schema, the description covers purpose and invocation conditions adequately. Nothing essential to selecting or calling the tool is missing, though sibling disambiguation would be a nice refinement.

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%, and the enum parameters (time_range, search_type) are documented in detail within the schema itself, so the baseline is 3. The description's example list ('recent news, stock prices, weather') gives mild intuition about what the query parameter accepts but adds no syntax or constraint detail beyond the schema.

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 web for current information, news, facts, prices, or events'), which clearly separates it from internal-retrieval siblings like knowledge_query or notes_search. It does not, however, explicitly differentiate itself from adjacent web siblings such as web_fetch, web_research, or web__local_search, so an agent still has to infer the boundary.

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 concrete trigger ('when the user asks about something that requires up-to-date information from the internet, or when internal knowledge base doesn't have the answer') plus illustrative examples. There is no explicit when-not guidance and no named alternative tool to route to, which keeps it short of a 5.

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