WebMCP Bridge exposes 2 tools with clear verb-noun naming (reference_read_counter, reference_increment_counter) and proper JSON Schema input definitions. Both tools have descriptions and constrained parameters. However, descriptions are minimal (under 100 chars), lack context about when to use each tool, and do not explain the relationship between them. Parameter descriptions are absent entirely. Output schemas are not documented. Error handling guidance is missing. The tools appear to be example/reference implementations rather than production-grade definitions.

• Expand tool descriptions to 100-200 characters. For reference_read_counter: 'Retrieve the current counter value from the page. Call this before incrementing to verify the current state or after an increment to confirm the update succeeded.' For reference_increment_counter: 'Increment the page counter by a specified amount (1-10). Useful for testing state mutations. Returns the new counter value and the amount applied.'
• Add parameter description for 'amount': 'The increment amount as an integer. Must be between 1 and 10 inclusive. Larger values are rejected by the server.'
• Document output schemas. Specify that both tools return an object with at least {counter: number} and clarify the counter's valid range (e.g., 0-1000).
• Add error handling guidance: 'If amount is outside 1-10, the server returns HTTP 400 with error message. Retry with a valid amount. If the counter reaches a limit, the server may reject further increments.'
• Clarify tool relationship in descriptions: 'These tools operate on shared page state. Use reference_read_counter to observe state, then reference_increment_counter to mutate it. Operations are not atomic across multiple calls.'