describe_tools is not used by LLMs, so description is misleading
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16
- Forks
- 3
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 121
Description
The LLMs don't currently use describe_tools unless directly prompted to, and they are not pointed to it unless they encounter an error using a tool. Users who write extended documenation in the tool description field - that is only exposed when describe_tools is run - are mislead. It is better to rename the field post_error_advice.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the Rust codebase for describe_tools and the tool description field, then trace where the field is declared and referenced. Rename the field to post_error_advice and update its references; the work is done when the name consistently reflects that the text is exposed as post-error guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai, cli
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100