Jarvis exhibits significant gaps in definition quality. While 6 tools are registered with basic descriptions and most have input schemas, the quality is inconsistent. Tool names mostly follow verb_noun convention, but descriptions are often generic (e.g., 'List resources from Google Drive' lacks context on when to use it). Parameter descriptions exist but are minimal and do not explain constraints, formats, or expected values. Output schemas are undocumented, no evidence of return type declarations. The 'list_tools' tool is a self-referential anti-pattern. Error handling is absent from visible code. The security posture is weak: no visible credential injection patterns, no permission gates, no audit trails. Only 1 of 6 tools (send_email) explicitly declares side effects.

• Add output schema documentation to every tool. For list_resources, document: { items: [{id, name, mimeType, uri, created}], nextCursor, totalCount }. For send_email: { messageId, timestamp, status }.
• Expand tool descriptions to 100-200 chars. For read_resource: 'Reads a Google Drive file by its gdrive:// URI. Use this after search() returns a URI, or when you have a Drive file link. Returns file content and metadata. Works for text, PDF, and images.'
• Add constraint descriptions to parameters. For search.query: 'Search terms (case-insensitive). Supports AND, OR, NOT operators. Max 1024 chars. E.g., "filename:budget AND mimeType:spreadsheet"'.
• Document pagination behavior. For list_resources: 'Returns up to 20 items per page. Use cursor from previous response to fetch next page. Omit cursor for first page. If nextCursor is null, you've reached the end.'
• Remove list_tools. It duplicates MCP's built-in discovery protocol and provides no value.
• Add error guidance. For send_email: 'On invalid email format, returns 400 with correction suggestion. On auth failure, returns 401, credentials may have expired; ask the user to re-authenticate. On send timeout, returns 504, safe to retry.'
• Implement dry-run for send_email. Add optional parameter dry_run (boolean, default false) with description: 'If true, validate recipients and format but do not send. Returns what would be sent.'
• For get_weather_info, clarify oneOf selection: 'Pass location as either a city name string (e.g., "San Francisco") for city-wide forecast, or as [latitude, longitude] for precise location. Ambiguous city names (e.g., "Portland") default to the most populous city.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry