execute_shell_command

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

Without annotations, the description fully discloses critical safety behavior: sandbox is integrity-only (confines writes, not reads), runs with user credentials, can read secrets and reach network unless deny_network is set, disabled by default, and output/runtime are bounded. This is exemplary transparency beyond what annotations would provide.

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?

The description is dense but efficiently structured: purpose first, then enabling, security criticals, and alternative. Every sentence carries distinct important information—no fluff, no repetition. It remains thorough without being bloated.

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?

Given the tool's high complexity, lack of annotations, and absence of an output schema, the description covers all essential context: purpose, security model, configuration, bounded behavior, and the safer alternative. Nothing important is omitted for an agent to safely invoke this tool.

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?

The schema already fully describes the 'command' parameter, including sh -c behavior, pipes/redirects/globs, an example, and workspace execution (100% coverage). The description adds no new parameter-specific meaning beyond the schema, so the baseline of 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 opens with a specific action: 'Run an ad-hoc shell command in the workspace via sh -c' with concrete examples and intent (verifying an edit compiles or tests pass). It distinguishes itself from the sibling 'run_command' by explicitly framing this as ad-hoc versus repeated use, making the purpose clear and differentiated.

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?

Provides explicit when-to-use guidance: for verifying an edit compiles or tests pass without leaving plumb. It also gives a clear when-not-to-use rule: 'Prefer run_command for anything you run repeatedly', plus necessary prerequisites (enable via config, plumb trust). This is more than sufficient.

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