A2CN MCP server defines 6 tools with complete input schemas and descriptions. Tool names follow verb_noun convention (a2cn_discover, a2cn_initiate_session, a2cn_send_offer, a2cn_accept, a2cn_reject, a2cn_get_session_status). All parameters have type definitions and descriptions. However, descriptions are minimal (10-50 chars), lacking context on WHEN to use each tool, prerequisites, or recovery guidance. No output schemas are documented, LLMs cannot predict response structure for chaining. Error handling is absent from tool definitions. Risk annotations (READ_ONLY, WRITE, IRREVERSIBLE) are present but not formalized as tool annotations in the MCP schema. Parameter descriptions lack format constraints, ranges, or examples of valid values.

• Expand tool descriptions to 100-200 chars. Include: what the tool does, when to call it (e.g., 'Call after a2cn_initiate_session to respond to a counterparty offer'), and what it returns. Example: 'Send a counteroffer in an active negotiation session. Call after receiving a counterparty offer via a2cn_get_session_status. Returns the updated session state and next expected response time.'
• Document output schemas for all tools. Specify fields, types, and whether results are paginated. Example for a2cn_get_session_status: '{"session_id": string, "state": enum[INITIATED|OFFER_SENT|OFFER_RECEIVED|ACCEPTED|REJECTED], "current_offer": {"total_value_cents": number, "payment_terms_net_days": number}, "counterparty_response_time_ms": number}'
• Convert deal_type parameter to a formal enum in the schema: ['saas_renewal', 'goods_procurement', 'services_engagement', 'logistics_rate']. Add similar enums for currency (ISO 4217 codes) and session state values.
• Add tool annotations to the MCP schema: mark a2cn_discover and a2cn_get_session_status with readOnlyHint=true; mark a2cn_initiate_session, a2cn_send_offer with destructiveHint=true; mark a2cn_accept and a2cn_reject with destructiveHint=true and idempotentHint=false (since they are irreversible).
• Implement a confirmation pattern for irreversible operations. Add a 'confirm' boolean parameter to a2cn_accept and a2cn_reject, or create separate tools (a2cn_confirm_accept, a2cn_confirm_reject) that require explicit confirmation after the agent has reviewed the offer.