MCASys exposes 5 tools with basic schemas and Chinese descriptions. All tools have input schemas with type definitions, but descriptions lack depth and actionable guidance. No output schemas documented. Parameters are minimally described. No error handling guidance, no idempotency hints, no permission declarations. Tool naming follows verb_noun convention (system_info, agent_status, task_create, task_list, task_status) but descriptions are generic and under 200 chars. Missing parameter constraints (enums for task type and status filters). No documentation of what fields are returned or how tools chain together. Schemas are present but sparse, task_create accepts 'params' as free-form object with no structure guidance.

• Document output schemas for all tools. E.g., task_create should return {task_id: string, name: string, type: string, status: string, created_at: ISO8601}. This enables LLMs to chain tools and extract required fields.
• Add enum constraints to task_list 'status' parameter: {type: 'string', enum: ['pending', 'running', 'completed', 'failed']}. Replace free-form descriptions with formal constraints.
• Define the structure of task_create 'params' object. Either provide a schema (e.g., {type: 'object', properties: {timeout: {type: 'integer'}, ...}}) or document valid keys in the description.
• Expand descriptions to 100-200 chars and include recovery hints. E.g., agent_status: 'Query the running status of one or more agents. If agent_id is omitted, returns all agents. If agent_id is not found, returns an error, try list_agents() first to discover valid IDs.'
• Add tool annotations (readOnlyHint, destructiveHint) to clarify side effects. Mark task_create as destructiveHint: false (it creates but does not delete). Mark system_info, agent_status, task_list, task_status as readOnlyHint: true.