Three tools with clear, actionable descriptions (avg 156 chars, within 10-1024 range). Tool names follow verb_noun pattern (request_*, check_*). No parameter descriptions visible in schema definitions. No output schemas documented. No error handling guidance (e.g., what happens if upload expires or fails). No tool annotations (readOnlyHint, destructiveHint). Descriptions are good but lack dependency hints and recovery guidance.

• Add explicit input schemas to request_upload and request_upload_interactive. Even if no parameters are required, declare an empty object with type: 'object', properties: {}, required: [] to signal intentional design.
• For check_upload, add format and length constraints to the 'id' parameter: e.g., pattern: '^[a-f0-9]{32}$' or minLength: 1, maxLength: 256. Include format hint in description: 'The upload record ID (alphanumeric, 1-256 chars)'.
• Document output schemas for all three tools. Define AwaitingUpload, UploadStatus, and InputRequiredResult structures with field types, descriptions, and examples. Include required fields for chaining (e.g., upload_id for check_upload).
• Add error handling guidance to descriptions. E.g., request_upload: 'If the upload URL expires (15 min), call this tool again to get a fresh URL.' check_upload: 'Returns status: issued, redeemed, completed, failed, expired, or unknown. If expired, request a new upload.'
• Add tool annotations to the schema. Mark all three tools with readOnlyHint: true since they do not modify state. This signals to agents that retries are safe.

Inferred effective spec: 2026-07-28+.

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