build_sandbox

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

No annotations provided, so description carries full burden. Discloses that it submits via qcmd if queue_walltime is set, takes ~1 hour, and is one-time. Could add more on error handling or file modifications, but sufficient for safe invocation.

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?

Four sentences, each adds essential information. Front-loaded with main purpose, then prerequisites, timing, and parameter details. No unnecessary words.

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 tool with 2 parameters and an output schema, the description covers purpose, prerequisites, behavior, and parameter semantics. Complete for an agent to select and invoke correctly given sibling tools include start_container.

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 has 0% description coverage and provides only defaults. Description adds meaningful defaults (~/scratch/crocontainer_sandbox for sandbox_dir, 3h for queue_walltime) and explains their intent, fully compensating for the schema's lack of description.

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?

Clearly states the tool builds an Apptainer writable sandbox from a crocontainer registry image. Uses specific verb (Build), resource (Apptainer writable sandbox), and context (on Derecho). Distinguishes from sibling tools like start_container.

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?

Explicitly says this is a one-time setup step required before start_container and mentions it takes ~1 hour. Provides context on when to use (before start_container) but could explicitly mention when not to use (e.g., after sandbox exists).

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