SmartGIU defines 4 tools with complete Zod schemas and descriptions in Portuguese. All tools have input schemas with type definitions and parameter descriptions. However, descriptions lack LLM-optimized guidance on when/why to use each tool, and output schemas are not documented. Tool naming follows verb_noun convention (conectar, buscar, executar, listar) but descriptions are verbose (200+ chars) and include implementation details (ChromaDB indexing) rather than user-facing intent. No error handling guidance, no pagination support for potentially large result sets, and no documented output structure for agents to plan downstream calls.

• Document output schemas for all tools. E.g., buscar_informacoes returns [{table_name, column_name, relevance_score}]; executar_query returns {rows: [...], row_count, execution_time_ms}. Include these in tool descriptions or as separate schema documentation.
• Add error handling guidance to descriptions. E.g., conectar_banco: 'If connection fails, verify host/port/credentials. Returns error with suggested next steps (e.g., check network, validate credentials).'
• Move credentials to server-side injection. Replace senha parameter with environment variable DB_PASSWORD. Document in README how to configure via .env or Docker secrets.
• Add pagination support to executar_query and listar_schema. Include limit (default 50, max 1000) and offset parameters. Return total_count so agents know if more results exist.
• Refactor descriptions to focus on user intent, not implementation. E.g., conectar_banco: 'Connects to a PostgreSQL database and indexes its schema for semantic search. Call this first before any query.' (60 chars, actionable).