Volnix provides 4 negotiation tools with basic schemas and descriptions. All tools have input schemas with required parameters and descriptions. However, descriptions are minimal (20-60 chars), lacking context on WHEN to use each tool, prerequisites, or what distinguishes them. Parameter descriptions are present but generic. No output schemas documented. No error handling guidance. Tools lack idempotency hints despite being state-modifying (WRITE risk). No tool annotations (destructiveHint, idempotentHint). The 'message' parameter across all tools is vague, unclear if it's mandatory, what format is expected, or how it affects negotiation state.

• Expand tool descriptions to 100-200 chars. Include WHEN to use (e.g., 'Call this to initiate a negotiation with an opening offer'), WHAT it does ('Sends your proposed terms to the counterparty'), and WHAT it returns ('Returns the counterparty's response or confirmation of receipt').
• Document output schemas for all tools. Specify fields like deal_status, current_offer, counterparty_response, timestamp. This enables LLMs to chain tools and track negotiation state.
• Clarify the 'message' parameter. Is it required? Does it affect negotiation logic or just provide context? Add format constraints (e.g., 'max 100 chars, plain text').
• Add error handling guidance. Document what happens if deal_id is invalid, negotiation is closed, or counterparty rejects. Provide recovery paths (e.g., 'If deal is closed, call list_active_deals to find an open negotiation').
• Add tool annotations: mark negotiate_accept and negotiate_reject as destructiveHint=true (they close deals); mark negotiate_propose as idempotentHint=true if calling it twice with the same terms produces the same result.