This is a template server with placeholder implementations. Both tools have basic schemas and descriptions, but lack depth and real functionality. Tool names are generic ('example-tool-1', 'example-tool-2') without action verbs. Descriptions are present but generic templates. Schemas are defined but tool implementations are stubbed (console.log only, no actual API calls). No error recovery guidance, no output schema documentation, and no parameter validation beyond basic JSON Schema. This is a starter template, not production-ready.

• Rename tools with action verbs: 'get_example_data', 'process_urls', or similar. Names must convey intent without reading the description.
• Replace template descriptions with concrete, LLM-optimized text (50-200 chars). State WHAT the tool does, WHEN to use it, and what it returns. Example: 'Fetch metadata for a list of URLs. Returns title, description, and status code for each. Use this to validate URLs before processing.'
• Document the output schema explicitly. Define what fields each tool returns, their types, and what they mean. Example: 'Returns {success: boolean, data: {title: string, status: number}, error?: string}'.
• Implement actual tool logic. Replace console.log and empty responses with real API calls, data processing, or business logic. Stub implementations block testing and agent reasoning.
• Add error recovery guidance. Catch specific error types and return actionable messages. Example: 'Invalid URL format. Expected http:// or https:// prefix. Retry with a valid URL.'