All three tools lack input parameter schemas entirely (empty {} for all), violating the critical requirement that every tool must have a documented input schema. Descriptions exist but are minimal (20-80 chars) and lack actionable context for LLM selection. No parameter descriptions, no output schema documentation, no error handling guidance. Tool names use non-English verbs (sistem_ozeti, kaynak_kullanimi, wan_ip_getir) which may confuse English-speaking LLMs. No tool annotations (readOnlyHint, etc.) despite all being read-only operations. This server falls well below production baseline.

• Add explicit input schemas to all tools. Even if a tool takes no parameters, declare 'input: {type: object, properties: {}, required: []}' to signal intentional zero-parameter design.
• Rename tools to English action verbs: sistem_ozeti → get_system_summary, kaynak_kullanimi → get_resource_usage, wan_ip_getir → get_wan_ip. This enables LLMs to infer intent from the name.
• Expand descriptions to 80 - 150 characters. Include WHEN to call the tool and what fields the response contains. Example: 'Get Ubuntu version, kernel, uptime, CPU model, core count, and virtualization status. Call this first to assess system health.'
• Document output schemas for each tool. Specify field names, types, and nesting. Example for sistem_ozeti: {surum: {pretty_name, version_id, version_codename}, kernel: string, uptime: {saniye: int, okunabilir: string}, cpu: {model: string, mantiksal_cekirdek_sayisi: int}, sanallastirma: {durum, tip?, vendor?, product?}}.
• Add readOnlyHint: true to all three tools in their definitions to signal to agents that these are safe to call without side effects.