Four tools with complete input schemas and descriptions, but quality varies significantly. trigger_manage has a complex, well-structured schema with nested objects and proper enums, but descriptions lack LLM-optimization guidance (194 chars baseline suggests 50-200 optimal). trigger_jobs and trigger_source have adequate schemas but minimal descriptions (under 100 chars). trigger_scheduler is skeletal. No output schemas documented. Error handling guidance absent. Parameter descriptions exist but lack actionable constraints (e.g., cron format, timezone validation rules). No tool annotations (readOnlyHint/destructiveHint/idempotentHint) despite WRITE risk labels.

• Add output schemas for all tools. Example: trigger_jobs schedule action should return {job_id: string, trigger_id: string, scheduled_at: ISO8601, status: enum}. Document which fields enable chaining to downstream tools.
• Enhance parameter descriptions with format rules and examples. E.g., cron: 'Five numeric fields (minute hour day month weekday), e.g., "0 9 * * 1" for 9am Mondays'. timezone: 'IANA timezone string, e.g., America/New_York'.
• Add tool annotations to schema. Mark trigger_manage create/update/delete as destructiveHint=true. Mark trigger_jobs list/status as readOnlyHint=true. Mark trigger_jobs schedule with idempotencyKey support as idempotentHint=true.
• Document parameter dependencies explicitly. E.g., 'For create action, prompt is required. For update, prompt is optional and only updates if provided. workspace and preset are immutable.'
• Add error recovery guidance to descriptions. E.g., trigger_manage: 'If trigger_id not found, call with action=list to discover available triggers.' trigger_jobs: 'If schedule fails with permission error, verify workspace-write permission is set.'