arch_exec_terminal_cmd

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

With no annotations, the description carries the full burden. It does disclose that it captures stdout, stderr, exit code, and handles timeouts, which is useful. However, it does not mention potential safety risks (e.g., commands can modify system state) or that it runs with user privileges, leaving an important transparency gap for a tool that executes arbitrary 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 two sentences, front-loaded with the core purpose. Every word earns its place; there is no filler or redundancy. It is as concise as possible while conveying key behavior.

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 a generic command executor with a simple schema (3 fields) and an output schema, so the return values are likely covered. The description mentions command capture and timeout handling, but omits cwd semantics, safety caveats, and usage guidance. It is not severely incomplete but has notable gaps for a potentially powerful 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?

Schema description coverage is 0%, so the description must compensate. The description implies the 'command' parameter ('Execute any terminal/CLI command') and mentions timeouts, which maps to 'timeout_seconds'. However, 'cwd' is not described at all, and no details are given about command syntax or argument handling, so compensation is partial.

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 'Execute any terminal/CLI command' with a clear verb and resource, and specifies 'in the user's shell environment' for context. It distinguishes itself from the sibling tools, which are specialized for specific operations (e.g., arch_systemctl, arch_journalctl), by being the generic command runner.

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 the specialized sibling tools. It does not mention alternatives, exclusions, or specific use cases (e.g., 'use for arbitrary commands; use arch_systemctl for systemd'). The only implied guidance is that it runs any command, but no explicit when/when-not guidance is given.

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