14 tools with consistent verb-noun naming (search_*, download_*, list_*, inspect_*) and structured schemas. All tools have descriptions (avg 85 chars, within baseline 34-392). Input schemas present with types and descriptions for all parameters. However, output schemas are NOT documented, responses are inferred from code (AssetDescriptor, release metadata). Error handling exists but lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Parameter descriptions are functional but minimal (10-30 chars typical). Missing: pagination guidance, per-item error reporting for batch operations, and explicit output schema documentation.

• Add output schema documentation to all download_* and inspect_* tools. Document AssetDescriptor fields (asset_id, variants, attribution, extra) and release metadata structure (repository, version, assets array with id/name/size/download_count).
• Implement tool annotations: add readOnlyHint=true to all search_*, list_*, inspect_* tools; add destructiveHint=true to all download_* tools (they write to disk). This enables agents to reason about side effects.
• Enhance error messages with recovery guidance. Replace 'Failed to search Game Icons' with 'Failed to search Game Icons: check query syntax (use hyphens, not underscores) or try a broader term. If persistent, verify GitHub API rate limits.'
• Expand parameter descriptions to include constraints and examples. E.g., 'Font variant (regular, bold, italic, bold-italic). Defaults to regular. Must match available variants for the selected family.'
• Document pagination and result limits in search tool descriptions. E.g., 'Returns up to 20 results by default (max 100). Use limit parameter to adjust. Results are sorted by relevance.'
• Add per-item error reporting for batch operations (e.g., if downloading multiple assets, return success/failure per asset rather than all-or-nothing).