run_command

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 only states that a bash command is executed and implies a developer-task scope, but it does not disclose side effects, blocking behavior, output/exit-code semantics, working directory, or safety implications of running arbitrary shell commands.

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 a single tight sentence with no filler. It front-loads the core action and adds a useful scope qualifier, making it appropriately sized for the tool's simplicity.

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?

The tool is simple and its two parameters are fully documented in the schema. However, there is no output schema, and the description does not mention what the command returns, whether it blocks by default, or how it should be preferred over sibling process/package tools, leaving some practical gaps.

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 100%, so the input schema already documents 'command' and 'background' clearly. The description adds little parameter-level meaning beyond confirming bash usage and developer-focused intent, which matches the baseline for fully-covered schemas.

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 ('Execute'), a resource ('bash shell command'), and an intended scope ('developer tasks (git, tests, builds, package managers)'). It is clear enough to separate from file/process/package tools, though it does not explicitly name any sibling or contrast its behavior with them.

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 phrase 'for developer tasks (git, tests, builds, package managers)' provides a clear context for when to use this tool. It does not state exclusions or explicitly point to alternatives like packagekit_install or process_list, so it falls just short of full when/when-not guidance.

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