Descriptions are present but generic (10-60 chars), below the 50-200 char LLM-optimized baseline. No parameter documentation exists. Tools lack error handling guidance, output schema documentation, and actionable recovery paths. The server exposes read-only discovery tools with minimal structure, appropriate for a configuration inspector, but implementation quality is far below production standards.

• Add explicit JSON Schema to all tools. E.g., platform.list_targets should declare input as {} (no params) and output as {type: 'object', properties: {platformName: {type: 'string'}, targets: {type: 'array', items: {type: 'object', properties: {id, kind, label, readonly, siteUrl, repository, roots}}}}}.
• Expand descriptions to 80-150 chars. Example: 'List all configured targets (WordPress sites, GitHub repos, filesystem roots, etc.) and their adapter types. Call this first to discover available resources before querying specific adapters.'
• Document output schemas in tool metadata. Add a 'returns' field or update descriptions to state: 'Returns a JSON object with platformName (string) and targets (array of {id, kind, label, readonly, siteUrl, repository, roots})'.
• Add error handling guidance. E.g., 'If a WordPress target is unreachable, the response will include an error field. Retry with remoteProbe=false or check network connectivity.'
• Clarify tool sequencing in descriptions. E.g., 'Call platform.list_targets first to see available adapters, then call adapter-specific tools (wordpress.describe_site, github.describe_repo) to inspect individual targets.'