Three tools with clear verb-noun naming (search_, inspect_, download_) and documented input schemas. Descriptions are present but generic (10-50 chars), lacking LLM-optimized guidance on WHEN to use each tool and what distinguishes them. Parameter descriptions exist but are minimal. Output schemas are not documented, LLMs cannot predict return structure. Error handling returns generic exceptions without recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Missing idempotency guarantees for download_blender_extension.

• Expand tool descriptions to 100-200 chars. Example: 'Search the official Blender extension repository by keyword. Returns matching extensions with metadata (id, name, version, tags). Use this to discover extensions before calling inspect_blender_extension for details.'
• Document output schemas for each tool. Example for search_blender_extensions: 'Returns {extensions: [{id, name, version, tagline, maintainer, license[], tags[], blender_version_min, blender_version_max, source_url}], count: int}'
• Enhance error messages with recovery guidance. Example: 'Extension not found: extension_id. Try search_blender_extensions(query=partial_name) to find the correct ID.'
• Add tool annotations: mark search_blender_extensions and inspect_blender_extension with readOnlyHint=true; mark download_blender_extension with destructiveHint=true.
• Document idempotency for download_blender_extension: 'Idempotent, calling with the same extension_id and output_dir will overwrite the previous download. Safe to retry on transient failures.'