Server provides 7 tools with complete input schemas and descriptions in Portuguese. Naming follows verb_noun pattern (despezzas_*) consistently. However, descriptions are brief (avg ~60 chars, well below the 194-char baseline) and lack context on WHEN to use each tool or what happens on failure. Parameter descriptions are minimal. Output schemas are not documented. Error handling guidance is absent. No confirmation/dry-run patterns despite 3 destructive/irreversible tools. Tool composition is reasonable but descriptions do not explain dependencies or prerequisites.

• Expand tool descriptions to 100 - 200 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. E.g., 'Switches the active profile for subsequent API calls. Use this before operations on a specific profile. Requires confirm=true. Returns the new active profile ID and name.'
• Document output schemas for all tools. Specify which fields are returned, their types, and which are safe to pass to downstream tools. E.g., despezzas_list_profiles should document that it returns an array of {profile_id, name, type, role} objects.
• Add error recovery guidance to tool descriptions. E.g., 'If authentication fails, the user must re-authenticate via the Despezzas web app. If profile_id is invalid, call despezzas_list_profiles() to discover valid IDs.'
• Enhance parameter descriptions for complex inputs. For 'invites' array, clarify: 'List of email addresses and roles to grant access. Replaces the current invite list entirely. Max 5 invites. Roles: editor (can modify profile), viewer (read-only).'
• Implement structured error responses that categorize failures. E.g., return {error: 'auth_required', message: 'Authentication expired. Please re-authenticate.', retryable: false} instead of a generic 500 error.