execute_shell

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains key traits: the tool executes shell commands, the starting directory is fixed per invocation, and full paths are needed for multi-step operations. This adds valuable context beyond the basic schema, though it could mention security implications or output handling.

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 front-loaded with the core purpose and examples, followed by important behavioral notes. It uses two sentences efficiently, with no wasted words. However, the first sentence is slightly verbose ('A tool capable of executing shell commands can use...'), and it could be more streamlined without losing clarity.

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 complexity (executing arbitrary shell commands) and lack of annotations or output schema, the description does a fair job. It covers the fixed starting directory and path advice, which are critical for usage. However, it misses details like error handling, security warnings, or output format, leaving gaps for a tool with significant behavioral implications.

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 description coverage is 100%, with the 'command' parameter well-documented in the schema. The description doesn't add specific syntax or format details for the parameter beyond implying it accepts shell commands like 'pwd' or 'cd'. Since the schema already covers the parameter adequately, a baseline score 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 states the tool 'executes shell commands' and provides examples (pwd, cd, ls, scripts), which clarifies its purpose. However, it doesn't distinguish this tool from potential siblings like 'execute_code'—both could involve command execution, leaving the differentiation unclear. The purpose is understandable but lacks sibling-specific context.

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 description includes a note about the starting directory being fixed and advises using full paths for multiple operations, which offers some usage context. However, it doesn't explicitly state when to use this tool versus alternatives like 'execute_code' or other siblings, nor does it provide exclusions or prerequisites. Guidance is minimal and not comparative.

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