Critical gaps across all dimensions. Of 24 tools, only 6 have visible input schemas in source (get_file_info, get_cad_entities, get_layers, get_cad_block_info, convert_cad_to_family, link_cad_files). 18 tools (create_level, create_grid, get_current_view_elements, etc.) have NO visible schema definitions, only handler file references. Descriptions range from absent to generic (e.g., 'Creates a new level in the Revit document' lacks parameters, constraints, return type). No parameter descriptions visible for most tools. No output schemas documented. No error handling guidance. No tool annotations (readOnlyHint/destructiveHint).

• Add explicit input schemas to all 18 tools lacking them. Use JSON Schema with type, description, and enum/pattern constraints for each parameter. Example: create_level should define {name: string, elevation: number, description?: string}.
• Write 50-200 character descriptions for all tools following the pattern: WHAT it does, WHEN to use it, WHAT it returns. Example: 'Creates a new level at the specified elevation. Use before placing elements on that level. Returns {levelId, name, elevation}.'
• Add parameter descriptions to all tools. Every parameter needs a description explaining its purpose, valid values, and constraints. Example: 'elevation (number): Height in feet (0-500). Required.'
• Document output schemas for all tools. Specify return type (object/array), field names, types, and whether fields are required. Example: get_file_info returns {projectName: string, linkedFiles: [{name: string, path: string}], elementCount: number}.
• Add tool annotations: mark all READ_ONLY tools with readOnlyHint=true; mark all WRITE tools with destructiveHint=true; mark idempotent tools with idempotentHint=true. This enables agents to reason about safety and retry logic.