Two tools with clear, detailed descriptions and well-formed schemas. Naming follows verb_noun convention (w3c_search, w3c_spec). Descriptions are 194 - 250 chars, within the 10 - 1024 baseline. Both tools have input schemas with type definitions and parameter descriptions. However, w3c_spec has a critical schema defect: required array is empty despite 'spec' being the only meaningful parameter. Output schemas are not documented, LLMs cannot predict response structure. Error handling is present but minimal (throws generic errors without recovery guidance). No tool annotations (readOnlyHint, idempotentHint). Search tool caps results at 25 (good), but detail tool lacks pagination guidance. Parameter descriptions are adequate but could specify format constraints more explicitly (e.g., 'shortname format: 2 - 20 alphanumeric chars').

• Fix w3c_spec schema: set required: ['spec'] to make the parameter mandatory and clear.
• Document output schemas for both tools. Example for w3c_search: { query: string, total_matches: number, count: number, specs: Array<{shortname, title, status, organization, url}>, source: string }.
• Enhance error messages with recovery guidance. E.g., 'w3c_search requires a query (e.g., "accessibility", "flexbox"). Try again with a keyword.'
• Add tool annotations to the schema: readOnlyHint: true and idempotentHint: true for both tools to signal safety to LLMs.
• Consolidate w3c_spec parameter aliases into a single 'spec' parameter in the schema and document in the description that it accepts shortnames, titles, or fragments.