The server defines 20 tools covering customer, lawsuit, transaction, and metadata management for Advbox. Tool names are consistently verb-prefixed (list_, get_, create_, update_) which is good (90% baseline compliance). However, definition quality is held back by: (1) inconsistent parameter descriptions, many tools have detailed schemas with descriptions (e.g., advbox_list_customers has 14 well-described params), but others are sparse (advbox_get_birthdays, advbox_get_settings, advbox_get_users, advbox_get_origins, advbox_get_groups, advbox_get_stages, advbox_get_types, advbox_get_steps all have empty input schemas with no descriptions); (2) absent output schema documentation, no tool documents what fields are returned, breaking downstream tool chaining; (3) missing error guidance, no tool describes what errors might occur or how to recover; (4) tool descriptions are brief (40 - 100 chars), mostly functional but lack LLM-optimization guidance on when to use each tool vs. similar ones. Per-tool analysis: tools 1 - 3, 5 - 7, 11 - 12 have solid input schemas (65 - 75 range); tools 4, 13 - 20 have empty inputs (0 - 30 range). All tools lack output schema definition, capping schema scores. Naming is consistent and clear throughout.

• Add structured output schema documentation to every tool. Example: advbox_get_customer should document 'Returns: {id (integer), name (string), email (string), phone (string), cellphone (string), ...}'. Use a JSON Schema response property or add to the description.
• Expand descriptions for discovery tools (get_settings, get_users, get_origins, get_groups, get_stages, get_types, get_steps) to 80 - 150 characters. Explain what data is returned and when to call each. Example: 'Returns a list of all available customer origins (e.g., Website, Referral, Direct) used when creating customers. Call this once to populate a dropdown.'
• Add error recovery guidance to 5 - 10 most critical tools. Example: advbox_get_customer → 'If customer not found, try advbox_list_customers() with name, email, or phone filters.' Use pattern:recovery-guide.
• Add per-parameter descriptions to advbox_get_users_rewards. Explain what 'date' filters (e.g., 'Filter rewards earned on or after this date (YYYY-MM-DD format)').
• Document pagination behavior in advbox_list_customers, advbox_list_lawsuits, advbox_list_transactions descriptions. State: 'Returns up to limit items (default 100, max 1000). Use offset for pagination. Returns paginated results.'
• Consider adding tool annotations (readOnlyHint, destructiveHint) to distinguish read-only tools from write operations. Helps LLMs prioritize safety in agentic reasoning.
• For advbox_create_customer and advbox_create_lawsuit, add confirmation/dry-run note in description: 'This creates a permanent record. Ensure all required fields are correct before calling.' Aligns with pattern:confirmation-request for irreversible operations.