Skip to content

Fix: set tool specification description to tool name when description is blank#214

Open
mnickel wants to merge 1 commit intoaws-samples:mainfrom
mnickel:feature/toolspec-description-cannot-be-blank
Open

Fix: set tool specification description to tool name when description is blank#214
mnickel wants to merge 1 commit intoaws-samples:mainfrom
mnickel:feature/toolspec-description-cannot-be-blank

Conversation

@mnickel
Copy link
Copy Markdown

@mnickel mnickel commented Dec 19, 2025

Issue #213 :

Description of changes:
When working with cline in VSCode, user reported seeing these errors:

[ERROR] Stream error: 500: Parameter validation failed:
Invalid length for parameter toolConfig.tools[13].toolSpec.description, value: 0, valid min length: 1

Amazon Bedrock requires a description property of a tool specification to be > 1 length

https://docs.aws.amazon.com/bedrock/latest/APIReference/API_agent_ToolSpecification.html

Rather than use a pydantic validator, i just added a simple inline to use the tool name as the description if necessary

Cline project has an issue under review:
cline/cline#7696

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

… is blank

When working with cline in VSCode, user reported seeing these errors:

[ERROR] Stream error: 500: Parameter validation failed:
Invalid length for parameter toolConfig.tools[13].toolSpec.description, value: 0, valid min length: 1

Amazon Bedrock requires a description property of a tool specification to be > 1 length

https://docs.aws.amazon.com/bedrock/latest/APIReference/API_agent_ToolSpecification.html

Rather than use a pydantic validator, i just added a simple inline to use the tool name as the description if necessary

Cline project has an issue under review:
cline/cline#7696
@zxkane
Copy link
Copy Markdown
Member

zxkane commented Dec 22, 2025

Thank you for the PR. However, I don't support this fix.

Tool descriptions are critical for agentic systems - they help LLMs select the right tools. As a proxy, this project shouldn't modify request content. This issue should be fixed by the tool provider (Cline).

I see you've mentioned cline/cline#7696, which is the right approach. Please address this upstream rather than working around it in the gateway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants