download_from_sandbox

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses key behaviors: file is read from /tmp, content returned as base64, and maximum file size of 10MB. It lacks details on error handling or explicit non-mutating nature, but 'Read' is a clear signal and the key constraints are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and resource, followed by the most critical constraint. Every word contributes; no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no annotations and no output schema, the description covers purpose, location, encoding, and size limit. It does not specify behavior on missing files or exceed size, but these are not essential for basic selection and invocation. Adequate and complete enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single 'filename' parameter, which already explains the format and location. The description reinforces that the file is in /tmp and adds output details (base64, size limit), but does not significantly add meaning to the parameter itself beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool reads a file from the sandbox container's /tmp directory and returns base64-encoded content. The verb 'Read' and specific resource location distinguish it from siblings like upload_to_sandbox and list_sandbox_files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is clear: this tool is for reading files from the sandbox. However, it does not explicitly say when to use it over alternatives like upload_to_sandbox or list_sandbox_files, nor does it mention exclusions. Still, the purpose implies usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.