This is a multi-server sample collection from AWS. Only 3 tools are visible in the provided source (auditCompliance, monitorMarketAbuse, updateComplianceRules). The code snippet is truncated mid-docstring for auditCompliance ('Audits the complian'). Critical gaps: (1) Tool descriptions are incomplete, auditCompliance's description is cut off; monitorMarketAbuse and updateComplianceRules lack any visible docstring in the source. (2) No input parameter descriptions are shown beyond the parameter names and types in the JSON schema. (3) Output schemas are completely undocumented. (4) No error handling guidance visible. (5) Tool naming uses adjective+noun (auditCompliance, monitorMarketAbuse) rather than verb_noun convention, making intent ambiguous. The FastMCP decorator (@mcp.tool()) is present, but the actual implementation is truncated, preventing full schema and behavior validation.

• Complete all tool descriptions to 50-200 characters, stating WHAT the tool does, WHEN to use it, and what it returns. Example: 'Audits a trade against compliance policies and returns a compliance status (passed/failed) with details on any rule violations.'
• Add descriptions to every input parameter. For tradeId: 'The unique identifier of the trade to audit (e.g., TRADE-12345).' For policyId: 'The ID of the compliance policy to update (e.g., POL-001).'
• Document the output schema for each tool. Example: auditCompliance should return '{compliance_status: string (passed|failed), violations: array of {rule_id, rule_name, severity}, audit_timestamp: ISO8601 string}'.
• Rename tools to follow verb_noun convention: audit_compliance or audit_trade, monitor_market_abuse or detect_abuse, update_compliance_rules. This makes intent explicit to LLMs.
• For updateComplianceRules, define a strict schema for newRules: array of objects with {ruleName: string, description: string, severity: enum(low|medium|high), ruleType: enum(market_abuse_detection, insider_trading, position_limit)}.
• Add error handling: return actionable errors like 'Trade TRADE-12345 not found. Call list_trades() to see available trades.' Categorize as retryable (network timeout) or user-fixable (invalid trade ID).
• Provide dry-run or confirmation support for updateComplianceRules (WRITE operation), allowing the agent to preview changes before committing.
• Document the risk level (READ_ONLY vs WRITE) in tool descriptions, especially for compliance-sensitive operations.