Skip to content

Commit 810f9ef

Browse files
olaservodsp-ant
andauthored
Update blog/content/posts/2025-09-22-using-server-instructions.md
Co-authored-by: David Soria Parra <[email protected]>
1 parent 10fbe45 commit 810f9ef

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

blog/content/posts/2025-09-22-using-server-instructions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ So now our question becomes: what's the most effective way to share this context
2727

2828
## Solutions
2929

30-
One solution could be to include extra information in every tool description or prompt provided by the server. Going back to the physical tool analogy, however: you can only depend on "labeling" each tool if there is enough space to describe them. A model's context window is limited - there's only so much information you can fit into that space. Even if all those labels can fit within your model's context window, the more tokens you cram into that space, the more likely it is that the output will be less than ideal.
30+
One solution could be to include extra information in every tool description or prompt provided by the server. Going back to the physical tool analogy, however: you can only depend on "labeling" each tool if there is enough space to describe them. A model's context window is limited - there's only so much information you can fit into that space. Even if all those labels can fit within your model's context window, the more tokens you cram into that space, the more challenging it becomes for models to follow them all.
3131

3232
Alternatively, relying on prompts to give common instructions means that:
3333

0 commit comments

Comments
 (0)