Server has 7 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (gofundme_*). Descriptions are present and substantive (100-300 chars), explaining WHAT the tool does and prerequisites. However, parameter descriptions lack detail on constraints (e.g., enum values for 'type', 'category', 'campaign_type', 'payer_chain' are stated in descriptions but not formalized as JSON Schema enums). Output schemas are not documented, callers must infer structure from descriptions. Error handling is basic (RuntimeError with API message). No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Security: API key is correctly injected via environment variable, not exposed as parameter. Composition is sound, each tool has one responsibility, and outputs contain IDs for chaining (campaign_id, contribution_id, agent_id).

• Add JSON Schema enum constraints for 'type' (autonomous|assistant|hybrid), 'category' (compute|infrastructure|research|community|creative|other), 'campaign_type' (self_fund|project_fund|community_fund), 'sort' (trending|newest|most_funded), and 'payer_chain' (base|solana|polygon|arbitrum|bsc|ethereum|monad|hyperevm). This prevents hallucinated values and makes valid options machine-parseable.
• Document output schemas for all tools. E.g., gofundme_register returns {agent_id: string, api_key: string, claim_url: string}. gofundme_discover returns {campaigns: [{id, title, goal_amount, funded_amount, category, deadline}], total: number}. Agents need to know what fields to extract.
• Add tool annotations: readOnlyHint=true for gofundme_discover, gofundme_my_campaigns, gofundme_campaign_status; destructiveHint=true for gofundme_register, gofundme_create_campaign, gofundme_contribute, gofundme_settle_contribution. This signals to agents which operations are safe to retry.
• Enhance error messages with recovery guidance. E.g., if API_KEY is missing, raise ValueError with message 'AGENT_GOFUNDME_API_KEY not set. Call gofundme_register first to obtain an API key.' If campaign not found, return 'Campaign {id} not found. Call gofundme_discover() to list active campaigns.'
• Add numeric constraints to parameter descriptions. E.g., 'goal_amount: USDC amount as string (min 0.01, max 1000000)'. 'deadline: ISO 8601 timestamp (must be in future)'. This guides LLM input validation and prevents out-of-range values.