FolderBridge provides 3 read-only tools with clear verb-noun naming (file_info, inspect_pptx, open_image). All tools have descriptions (194 - 250 chars, within baseline 34 - 392 range) and input schemas with type definitions. However, parameter descriptions are sparse or missing entirely. file_info lacks parameter descriptions; inspect_pptx and open_image have minimal descriptions for optional params (e.g., 'optional' without explaining what max_width does or its valid range). Output schemas are not documented, LLMs cannot predict return structure. Error handling is present in code (ToolError with codes like NOT_FOUND, FILE_TOO_LARGE) but not surfaced in tool definitions. No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Composition is sound, each tool has one responsibility, but parameter naming could be more explicit (e.g., 'format' should be 'output_format' to avoid confusion with input format).

• Add detailed parameter descriptions to all tools. For inspect_pptx: 'page_start: Starting slide number (1-indexed, optional). If omitted, defaults to first slide.' For open_image: 'max_width: Maximum output width in pixels (1 - 4096, optional). Preserves aspect ratio if max_height also specified.'
• Document output schemas in tool descriptions. E.g., file_info returns {path, size, sha256, mime_type, content_encoding, modified_ns, is_file}. inspect_pptx returns {slide_count, selected_slides, diagrams, anomalies}.
• Add readOnlyHint: true and idempotentHint: true to all tool definitions to signal safety and enable client-side caching.
• Rename 'format' parameter in open_image to 'output_format' and add enum constraint: ['png', 'jpeg', 'webp', 'bmp']. Document in description: 'Output image format. Defaults to original format if omitted.'
• Enhance error messages in code to include recovery hints. E.g., FILE_TOO_LARGE should suggest 'File exceeds 2GB limit. Try splitting into smaller files or use inspect_pptx with page_start/page_end filtering.'