This server has 43 tools with consistent naming conventions (verb_noun pattern) and basic parameter schemas. However, the implementation suffers from critical gaps: (1) Parameter descriptions are minimal or absent for many tools, most 'filter' and 'updates' parameters lack detail on what fields they accept; (2) Output schemas are completely undocumented, the code returns JSON but provides no schema definition to LLMs about response structure; (3) Error handling is generic and non-actionable; (4) Many parameter types are overly generic (object types for 'filter' and 'updates' with no schema constraints). While tool names follow verb_noun conventions (list_assets, create_asset, delete_asset), the LLM cannot understand what fields are valid in a filter object or what structure to expect from responses. This forces the agent to guess at parameters and misinterpret results. The two read-only external API tools (list_manual_sales, get_manual_sale, etc.) have clearer intent but still lack output schema documentation.

• Document output schemas for all tools. For each tool, add a 'Returns' section specifying field names, types, and structure. E.g., 'Returns object with fields: id (string), name (string), status (enum: active|archived|deleted), created_at (ISO 8601 string).'
• Replace generic 'object' parameters with explicit enum or typed options. For update_asset, specify: 'updates: object with optional fields: name (string), description (string), status (enum: draft|active|archived), workflow_id (string).' Similar for update_task, update_phase, update_task_progress.
• Expand filter parameter descriptions with examples and valid field names. E.g., 'filter: optional object with fields: status (enum: active|archived), created_after (ISO 8601), created_before (ISO 8601), owner_id (string). Example: {"status": "active", "created_after": "2024-01-01"}'
• Add tool annotations. Mark delete_asset with destructiveHint=true, all write operations with idempotentHint=false (unless idempotent), and all read-only tools with readOnlyHint=true.
• Enhance error messages to be actionable. Instead of generic 'Error executing tool', return specific guidance: 'Asset not found. Call list_assets to see available assets.' or 'Invalid status value: got "pending_review", valid values are: draft, active, archived, deleted.'
• Add confirmation/dry-run pattern to delete_asset. Introduce a 'dry_run' parameter (boolean, default false) or a separate 'preview_delete_asset' tool that shows what would be deleted without executing.
• Enforce and document pagination limits. Add to list_* descriptions: 'Maximum limit is 100 records per request. Default limit is 20. Use skip parameter for pagination.'

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

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