Keep bulk data out of the LLM context: offload AI SDK tool results into a sandboxed just-bash workspace, and deliver formatted files straight to the user.
Four tools with clear names and reasonable descriptions, but significant gaps in schema completeness and parameter documentation. The bash tool lacks input validation guidance; readFile/writeFile have minimal parameter descriptions; sendFileToUser has good description but no output schema documented. Error handling is present but generic. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Average tool description ~120 chars (within baseline 194 chars), but parameter descriptions are sparse.
Execute bash commands in a sandboxed just-bash workspace. Provided by bash-tool library.
Read a file from the virtual filesystem. Provided by bash-tool library.
Send an already formatted text file (Markdown, CSV, plain text) from the virtual filesystem straight to the user. Format the final, user-ready output with bash first, then call sendFileToUser once. Do not repeat the delivered content in your final answer: the user already received it. Relative paths resolve against /workspace.
Write a file to the virtual filesystem. Provided by bash-tool library.
bash tool lacks input validation guidance. Description does not specify constraints on command length, timeout behavior, or what commands are blocked in the sandbox. LLMs cannot infer safe vs unsafe commands.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. bash and writeFile are destructive but unmarked; readFile and sendFileToUser are read-only but unmarked. Agents cannot reason about safety without explicit hints.
sendFileToUser output schema not documented in source. SinkToolOutput interface exists (sent, path, characterCount) but is not visible in tool registration or description. LLMs cannot plan downstream actions without knowing return structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
readFile and writeFile parameter descriptions are minimal (single sentence). No guidance on file size limits, encoding, path traversal prevention, or error recovery.
bash tool description references 'sandboxed just-bash workspace' but does not explain what commands are available (python3, js-exec, standard Unix tools) or what is blocked (network by default). Discovery is unclear.