feat: double the truncation limit

What does this merge request do and why?

Current truncation limit is quite low, we can be safe to double it to avoid unnecessary tool response truncation while still keep the low risks of exceeding the context window limit and payload size. #1594 (comment 2866003069)

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request checklist

  • Tests added for new functionality. If not, please raise an issue to follow up.
  • Documentation added/updated, if needed.
  • If this change requires executor implementation: verified that issues/MRs exist for both Go executor and Node executor or confirmed that changes are backward-compatible and don't break existing executor functionality.

Merge request reports

Loading