Scoring was not performed

• Add output schema documentation to every tool description. Example: 'Returns a list of events with fields: id (string), subject, start (ISO 8601), end (ISO 8601), attendees (array of email strings).'
• For destructive operations (delete-event, onedrive-delete), add confirmation-request pattern: 'Requires explicit confirmation. Call with confirm=true only after user approval.'
• Enhance error guidance in descriptions. Example for send-email: 'On failure, check recipient addresses, verify attachments exist, or try draft-email to save for later.'
• Add range constraints to numeric parameters in descriptions. Example: 'count' → 'Number of items to retrieve (1-50, default 10)'. Add 'sequence' → 'Execution order (0-999, lower runs first)'.
• Document mutual exclusivity for parameters. Example for onedrive-download: 'Either itemId or path is required; providing both may cause ambiguity.'
• Add enum constraints to status/type parameters. Example: importance → 'normal|high|low' (already present, good pattern).
• Clarify folder/email identifier handling. Example: 'targetFolder accepts folder name (e.g., "Archive") or internal ID. Use list-folders first if unsure.'
• Remove or deprecate the 'includeRawHtml' parameter in read-email, or document strict conditions: 'DANGEROUS: Only use for offline debugging with sanitized content. Never expose to LLM in production.'
• For flow-run, add discovery guidance: 'Call flow-list first to get flowId. Consult Power Automate UI to determine required inputs for your specific flow.'