Bash

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says that commands execute and output is returned. It hints at side effects through 'creating files, directories,' but does not disclose arbitrary filesystem mutation, destructive potential, shell environment, working directory, or error behavior.

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 short and front-loaded with the core behavior, but it repeats 'This function' and 'bash commands' across two sentences. The phrase 'and other bash commands' is redundant and adds little value.

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 one-parameter tool, the basics of input and output are present. However, because annotations are absent and there is no output schema, the description should provide more context about side effects, execution environment, and error handling, especially for a potentially destructive tool like bash.

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%, so the description must compensate. It does add some meaning by explaining that 'command' is a bash command and giving examples, but it stops short of providing syntax, quoting, multiline command handling, or execution context details.

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 clear action and resource: 'execute a bash command and return the output.' It also gives concrete examples like creating files and directories, which helps distinguish it from siblings such as read_file or python_code, though it does not explicitly name alternatives.

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 only usage guidance is that the function is 'useful for executing bash commands,' which is largely a restatement of its purpose. It does not explain when to prefer bash over siblings like write_file, create_folder, or python_code, and offers no exclusions, prerequisites, or safety conditions.

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