Search the public web for current or external information and return titles, URLs, and short snippets; use it before fetching a page when the exact URL is unknown.
Search the public web for current or external information. Returns titles, URLs and short snippets. Use before fetch_url when you do not know the exact page.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| max_results | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It does state the return shape (titles, URLs, short snippets), which is valuable, but says nothing about result freshness, rate limits, authentication, or what happens when zero results are found.
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?
Three short sentences, front-loaded with purpose and then return shape, then routing. No filler and nothing buried.
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 simple two-parameter search tool the description covers purpose, return shape, and sibling routing, but leaves the second parameter undocumented and gives no hint about result quality, freshness, or failure modes. Adequate to invoke, not fully 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 0%, so the description must compensate and does not: the query parameter is only implied by the word 'Search', and max_results (default 5, max 8) is never mentioned. An agent gets no guidance on query formatting or how result count affects cost or latency.
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 public web') plus the scope of information it targets ('current or external'). It explicitly contrasts with the sibling tool fetch_url, so an agent can choose between them without opening either schema.
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?
Provides an explicit decision rule: use this before fetch_url when the exact page is unknown. The alternative tool is named and the condition that selects it is stated, which is exactly the routing guidance an agent needs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.