Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Both tools have descriptions (10-20 chars baseline met), but lack depth on WHEN to use them and what they return. Input schemas are present with type definitions, but parameter descriptions are minimal. No error handling guidance, no output schema documentation, and no indication of idempotency or side effects. Naming follows verb_noun convention (create_, get_) which is good, but descriptions do not explain prerequisites, return structure, or recovery paths.

• Expand tool descriptions to 100-200 characters. Include: what the tool does, when to call it, what it returns, and any prerequisites. Example: 'Create a new NFT collection on Enjin Platform. Requires valid API key (set via ENJIN_API_KEY env var). Returns collection ID. Idempotent: calling twice with same name returns same ID. Use get_collection to verify creation.'
• Document output schemas explicitly. For create_collection, return {type: 'object', properties: {collection_id: {type: 'string', description: 'Unique ID of created collection'}, status: {type: 'string', enum: ['success', 'error']}}}. For get_collection, document all fields returned (maxTokenCount, royalty, owner, etc.) with types and descriptions.
• Enhance parameter descriptions with format and constraints. Example: 'name: string, 1-255 characters, alphanumeric + spaces, must be unique within account' instead of 'Name of the collection'.
• Add error classification and recovery guidance. Instead of returning raw error, categorize as retryable (network timeout → retry in 5s) or user-fixable (invalid collection_id → call get_collection to list valid IDs). Return structured error: {error: string, code: string, retryable: boolean, suggestion: string}.
• Declare side effects and idempotency. Add to create_collection description: 'DESTRUCTIVE: Creates a new collection on-chain. Idempotent: same inputs always produce same collection_id. Confirm before calling in production.' Add to get_collection: 'READ-ONLY: No side effects. Safe to call repeatedly.'