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

With no annotations beyond the title, the description carries full transparency burden. It discloses that it runs in a container, supports pipes/redirection/&&, working directory /work with persistence, and that non-zero exit codes are returned as data not errors. This is rich, accurate behavioral context.

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, front-loaded with the core action and environment, then use cases and exit-code behavior. No filler, every sentence contributes valuable information. Excellent structure.

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 without output schema, it explains return behavior (what it wrote, non-zero exit code in response), environment constraints, and typical usage. It is complete enough for an agent to call it correctly without missing critical expectations.

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% and each parameter already has a helpful description, including an example command. The description adds some context (working dir persistence), but the schema already documents dir and timeout defaults. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a specific verb ('run a shell command on your own machine') and resource, and distinguishes it from shell_list/read/write siblings. It also lists concrete use cases (build, test, run scripts, move files), so an agent can tell exactly what this tool does.

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?

It gives clear context on when to use it ('Use it to build, test, run scripts and move files about') and highlights the environment (container, /work). It does not explicitly mention when not to use it or point to alternatives, but the purpose is distinct enough from the shell_* siblings that the guidance is adequate.

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