{"version":"2.1.281","anchor":"tool-names-over-200-characters-are-truncated","canonical_anchor":"tool-names-over-200-characters-are-truncated","heading":"Tool names over 200 characters are truncated","tier":"notice","area":"Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/tool-names-over-200-characters-are-truncated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Tool names over 200 characters are truncated\n\nTool names longer than 200 characters are now cut to 200 instead of being passed through\n\n**What**\n\nThe repair of malformed responses now also covers tool names that are too long. When a request to use a tool (a `tool_use` block) names a tool with more than 200 characters, the name is cut to its first 200 characters. That shortened name is used to find the tool and is kept in the returned block. A warning is logged, and `tengu_content_block_healed` is reported with the action `name_truncated`.\n\nThe same limit is applied when saved conversation history is cleaned up:\n\n- `dropApiInvalidAssistantBlocks` shortens overlong names in the transcript to the API's limit and reports a `tool_name_truncated` outcome.\n\n- History cleanup counts shortened names in a new `truncated` tally, and a helper reports `overlongToolNames` alongside `foreignBlocks`.\n\n**Why**\n\nThe Anthropic API rejects tool names over 200 characters in requests, so one overlong name in the history could otherwise stop the conversation from being sent again.\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}