Improve verbosity of pretty_repr for tool calls

[mjclarke94]

Checked

• I searched existing ideas and did not find a similar one
• I added a very descriptive title
• I've clearly described the feature request and motivation for it

Feature request

Add details of the call_id and args to the pretty_repr of ToolMessage() objects.

Motivation

A common pattern is getting an agent to dispatch multiple tool calls in parallel, reducing latency when gathering information. When printing the stream arising from this pattern, it is not apparent which tool message corresponds to which tool call, and async calls would not necessarily preserve ordering.

================================ Human Message =================================

What is the weather in Tokyo and Kyoto?

================================== Ai Message ==================================
Tool Calls:
  get_weather (call_mSTvvPfGuJcMPTTQ7eHNyLit)
 Call ID: call_mSTvvPfGuJcMPTTQ7eHNyLit
  Args:
    city: Tokyo
  get_weather (call_7GUaz15eVKJNd7mw6OqYAsgB)
 Call ID: call_7GUaz15eVKJNd7mw6OqYAsgB
  Args:
    city: Kyoto

================================= Tool Message =================================
Name: get_weather

rainy

================================= Tool Message =================================
Name: get_weather

sunny

Modifying the repr for these calls to include a reference to the call_id eliminates ambiguity and makes these responses more meaningful when viewed in isolation.

Proposal (If applicable)

Include the call_id in the pretty_repr:

================================ Human Message =================================

What is the weather in Tokyo and Kyoto?

================================== Ai Message ==================================
Tool Calls:
  get_weather (call_mSTvvPfGuJcMPTTQ7eHNyLit)
 Call ID: call_mSTvvPfGuJcMPTTQ7eHNyLit
  Args:
    city: Tokyo
  get_weather (call_7GUaz15eVKJNd7mw6OqYAsgB)
 Call ID: call_7GUaz15eVKJNd7mw6OqYAsgB
  Args:
    city: Kyoto

================================= Tool Message =================================
Name: get_weather (call_mSTvvPfGuJcMPTTQ7eHNyLit)

rainy

================================= Tool Message =================================
Name: get_weather (call_7GUaz15eVKJNd7mw6OqYAsgB)

sunny

Ideally for readability the args supplied to the function would also be included, but these are not currently present in the ToolMessage object and modifying this would have more surface area. This approach seems fairly non-disruptive by comparison.