Two tools with minimal descriptions (10-20 chars each), basic parameter schemas lacking depth, and no output schema documentation. Naming is acceptable (verb_noun pattern), but descriptions are too terse to guide LLM selection. No error handling guidance, no parameter constraints (enums, ranges), and no documentation of return structures. Parameters lack descriptions entirely in the schema definitions visible in main.py. This server falls in the F-D range due to incomplete definitions and missing LLM-critical metadata.

• Expand tool descriptions to 50-150 characters. Example: 'report_bug: Create a new bug report with a title and description. Returns the unique bug ID for reference in future calls. Use this when a user reports a new issue.'
• Add parameter descriptions to all inputs. For bug_id, specify: 'The unique identifier (UUID format) of the bug to resolve. Obtain from report_bug response or list_open_bugs resource.'
• Return structured JSON from both tools. report_bug should return {"bug_id": "<uuid>", "status": "open", "created_at": "<iso8601>"} instead of a plain string.
• Add error handling with recovery hints. resolve_bug should return {"error": "Bug not found", "suggestion": "Call list_open_bugs to see available bug IDs"} on failure.
• Document output schemas in tool descriptions. State: 'Returns a JSON object with fields: bug_id (string), status (string: open|resolved), created_at (ISO 8601 timestamp).'