Two tools with reasonable naming (verb_noun pattern) and documented schemas. web_search has comprehensive parameter descriptions and enum constraints (search_depth). web_fetch has clear parameter documentation. However, both tool descriptions are moderately detailed but lack explicit guidance on when to use each tool vs. alternatives, and neither documents output schema structure. Parameter descriptions are present but some lack format/constraint details (e.g., 'query' lacks length guidance). No error handling guidance visible in definitions. Missing tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations.

• Document output schemas for both tools. Specify that web_search returns an array of {title, link, snippet, source} objects and web_fetch returns {content, url, title, metadata}. Include field types and whether fields are always present.
• Enhance tool descriptions with selection guidance: 'Use web_search to find information across multiple sources; use web_fetch to extract full content from a specific URL. web_search supports multiple engines and query expansion; web_fetch is faster for known URLs.'
• Add readOnlyHint: true to both tool schemas to signal they are safe to call repeatedly without side effects.
• Constrain the 'query' parameter: add description 'Search query string (1-500 characters, alphanumeric and common punctuation)' and consider a maxLength in the schema.
• Add error recovery guidance to descriptions: 'If a search returns no results, try simplifying the query or changing the search_depth. If web_fetch fails, verify the URL is accessible and try a different source.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry