controldctl exposes 11 tools with consistent naming (verb_noun pattern: devices list, profiles create, etc.) and complete input schemas. However, descriptions are minimal (10-30 chars), parameter descriptions lack detail on constraints/formats, and output schemas are not documented. Tool names follow action-verb convention well, but descriptions fail to explain WHEN to use each tool or what the LLM should expect in responses. No error handling guidance, no pagination info for list operations, and no documentation of which fields are returned.

• Expand all tool descriptions to 100-200 chars. Example: 'devices list' → 'Retrieve all configured devices (endpoints) for this account. Returns device ID, name, assigned profile, and status. Call this first to discover available devices before creating or updating.'
• Add constraint details to parameter descriptions. E.g., 'device name (required, 1-255 chars, alphanumeric + spaces)' and 'profile-id (required, UUID format, obtain via profiles list)'.
• Document output schemas in tool descriptions. E.g., 'Returns: {devices: [{pk, device_id, name, status, profile_pk, profile_name, created_at}]}'.
• Add error recovery guidance. E.g., 'devices delete: If device not found, call devices list to verify the device ID exists.'
• Add pagination to list tools: 'devices list' should accept optional limit (default 20, max 100) and offset parameters, and return total_count in response.