Velloo exposes 73 tools with minimal schema visibility. Tool definitions are inferred from tool-policy.ts (names and risk levels only); actual parameter schemas, input/output types, and detailed descriptions are not visible in the provided source. Per the hard rules, tools without visible schemas score 0 on schema; descriptions are generic one-liners (10-30 chars), scoring 0-20. No evidence of parameter type definitions, enum constraints, or error recovery guidance. The server is HTTP-based (good for transport), but definition quality is severely compromised by lack of schema documentation and shallow descriptions.

• Add full JSON Schema input definitions for all 73 tools. Include type, description, enum constraints, and required fields for every parameter. Current state: 0% coverage.
• Expand tool descriptions to 50-200 characters. Explain WHAT the tool does, WHEN to use it, and any prerequisites. Example: 'find_nodes' → 'Search for design nodes by name, type, or property. Use this to locate specific UI elements before inspecting or modifying them.'
• Add parameter descriptions for all tools. For each parameter, state its type, valid values/ranges, and dependencies. Example: 'node_id (string, required): The unique identifier of the node to inspect. Obtain from find_nodes() or list_components().'
• Implement confirmation/dry-run patterns for destructive tools (remove_*, delete_*). Return a confirmation_required error with a confirm_operation() tool to prevent accidental data loss.
• Document output schemas for all tools. Specify return type (object, array, string), field names, types, and which fields are needed for chaining to downstream tools. Example: 'Returns {node_id, parent_id, type, name}' so agents can chain to update_props().