shell

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

With no annotations, the description carries the full burden of disclosing behavioral traits, but it only says 'Run an allowlisted shell command.' It fails to mention potential side effects, output format, error handling, security implications, or the fact that this could modify the system. 'Allowlisted' hints at some restriction but lacks detail, leaving significant ambiguity for a powerful tool.

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 concise—a single sentence with no fluff—which is positive. However, it is under-specified to the point of being almost unhelpful. Concision is valued, but here it sacrifices necessary detail, making it only minimally acceptable.

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 that this tool executes arbitrary system commands, the description is critically incomplete. It lacks information about the execution environment, command output, exit codes, security restrictions, timeout behavior, and interaction with 'cwd'. With no annotations or output schema, the description fails to provide a complete picture, making safe and effective use nearly impossible.

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 description coverage is 0%, and the description does not compensate. Parameters like 'cwd', 'timeout', and even 'command' are not elaborated in any way. The description doesn't clarify that 'command' is the executable string, 'cwd' sets the working directory, or 'timeout' limits execution time. This leaves users without meaningful guidance on how to structure invocations.

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's primary function: to run a shell command. The verb 'Run' is action-specific and 'shell command' identifies the resource. While it doesn't elaborate on what 'allowlisted' entails, it distinguishes itself from siblings like web_search or fetch_url, which perform other actions.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like executing system-level commands or interacting with the local environment, nor does it specify any prerequisites or exclusions. Users are left to infer its context from the tool name alone.

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