Every Logos tool describes itself in one short line instead of a paragraph - #23
Merged
Merged
Conversation
…nt are one short line each instead of a paragraph
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tool and parameter descriptions were paragraphs; some hosts send every one on every request. Each tool now gets one line (≤200 chars) and each parameter ≤120, like a CLI's help. tools/list goes from 18,896 to 11,322 bytes (~4.7k → ~2.8k tokens).
The rules that exist because of past bugs survive in short form, and
tools_terse_test.gopins them: the receipt relay, remember's review-queue caveat, ingest_distil's turn citation and no-file-edit rule, and BEFORE on before_you_try/why/checkpoint.Also shortened: the server instructions (LOGOSPROMPT.md, 4,941 → 2,295 bytes), the SessionStart hook preamble, and the italic lines around results (provenance boundary, budget footer, empty-window, dead-end no-record, why footer). Tests cap each one and pin the rules they must keep.