execute_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 effectively adds context beyond what the input schema offers by explaining permission controls based on configuration, default allowances for read-only commands, and guidance on using 'cd'. However, it lacks details on potential side effects (e.g., destructive commands), error handling, or output format, which are important for a command execution 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 front-loaded with the core purpose, followed by essential usage notes in three concise sentences. Each sentence earns its place by addressing key aspects: execution context, permission controls, allowed commands, and handling of 'cd'. There is no redundant or verbose language, making it highly efficient.

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 complexity of executing terminal commands (which can have security and side-effect implications), no annotations, and no output schema, the description is moderately complete. It covers purpose, basic usage, and permissions but lacks details on output structure, error cases, or advanced behavioral traits. This leaves gaps for an AI agent to fully understand the tool's behavior in practice.

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 input schema has 100% description coverage, providing clear documentation for both parameters. The description adds minimal value beyond the schema by implying that 'working_directory' can be used as an alternative to 'cd', but it does not elaborate on parameter interactions, constraints, or examples. Baseline 3 is appropriate since the schema handles most of the parameter semantics.

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 specific action ('execute a terminal command') and resource ('on the host machine'), distinguishing it from siblings like 'approve_command' (which suggests a permission step) or 'change_directory' (which focuses on navigation). It provides a concrete verb+resource combination that leaves no ambiguity about the tool's core function.

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 offers clear context for usage by mentioning that 'read-only commands like ls, cat, git status are generally allowed by default' and advises on handling 'cd' via a separate command or the working_directory parameter. However, it does not explicitly state when to use this tool versus alternatives like 'approve_command' or 'change_directory', nor does it provide exclusions or prerequisites beyond the implied permission controls.

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