Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. read_last_release has no input parameters (empty schema). create_pdf has well-defined parameters with types and descriptions (good baseline). send_release_to_discord has parameters but lacks output schema documentation. No tool includes error recovery guidance, actionable error messages, or idempotency hints. Naming is clear (verb_noun pattern), but descriptions are brief (10-50 chars) and lack context on when/why to use each tool. No tool annotations (readOnlyHint, destructiveHint) despite clear risk profiles.

• Add explicit output schema documentation to all tools. E.g. create_pdf should document: {success: bool, file: string, path: string}. read_last_release should document the structure of the release JSON it returns.
• Expand tool descriptions to 50-200 chars. E.g. read_last_release: 'Retrieves the most recent release payload from the release_data directory. Call this first to fetch the latest release metadata before generating PDFs or sending notifications.'
• Add error recovery guidance. E.g. read_last_release error: 'No release files found in release_data/. Ensure release JSON files exist in the expected directory before retrying.'
• Annotate tools with risk hints. Mark create_pdf with destructiveHint=true (writes files), send_release_to_discord with destructiveHint=true (external side effect). Mark read_last_release with readOnlyHint=true.
• Document parameter constraints in descriptions. E.g. version parameter: 'Semantic version tag (e.g. v1.2.0). Must match the pattern v[0-9]+\.[0-9]+\.[0-9]+.'