TaroCub defines 8 tools with explicit schemas and descriptions, but quality is inconsistent. All tools have descriptions (10-200 chars, within baseline), and input schemas are present with type definitions. However, parameter descriptions are sparse or missing context. send.* tools lack guidance on error cases (file not found, permission denied). cron.* tools have better structure but lack idempotency hints and confirmation patterns for destructive operations (cron.remove). No tool declares permissions or audit requirements despite WRITE/DESTRUCTIVE risk levels. Output schemas are not documented, agents cannot predict response structure for chaining. Error handling is absent: no recovery guidance, no actionable error messages shown in code.

• Document output schemas for all tools. Example: cron.list should return {tasks: [{id: string, prompt: string, schedule: string, enabled: boolean, nextRun: string}], total: number}. This enables agents to extract task IDs for cron.remove/cron.toggle.
• Add parameter descriptions with constraints. For 'path' params: 'Absolute file path (must exist, readable by bot user, no symlinks). For 'query' in cron tools: 'Substring search in task prompt/description. Case-insensitive.'
• Implement confirmation pattern for cron.remove: add optional 'confirm: true' parameter. Return {confirmed: false, taskId: string, prompt: string} if confirm is false, requiring a second call with confirm=true. Prevents accidental deletion.
• Add error handling with recovery guidance. Example: 'File not found at /path/to/file. Verify path is absolute and readable. Use send.batch with empty arrays to test connectivity.' Return structured errors: {error: string, code: 'FILE_NOT_FOUND'|'PERMISSION_DENIED'|'INVALID_CRON', suggestion: string}.
• Declare tool permissions and audit requirements. Add metadata: send.* tools require 'write:telegram', cron.* tools require 'write:schedule'. Document that all WRITE/DESTRUCTIVE operations are logged with user ID, timestamp, and parameters for compliance.