execute_command

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

With no annotations provided, the description must disclose behavioral traits. It mentions 'security validation' but does not elaborate on what that entails, potential side effects, failure modes, or resource impact. This is a significant gap for a tool that executes arbitrary commands, which is inherently risky.

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, direct sentence with no redundancy. It efficiently communicates the core action. However, it is so brief that it omits crucial behavioral and usage details, which reduces its overall effectiveness. The brevity is not inherently flawed, but it sacrifices needed context.

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 tool's complexity and risk (command execution with security validation), the description is grossly incomplete. It fails to explain return values, timeout behavior, working directory effects, security levels, or any failure handling. With no annotations and no output schema, this description carries the full burden and falls far short.

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 provides complete descriptions for all four parameters, so the baseline is 3. The description adds no additional parameter-level meaning beyond what the schema already defines, and it doesn't clarify how 'security validation' relates to the security_level parameter.

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 function: executing a command in the terminal. This is a specific verb+resource pairing. While it doesn't explicitly distinguish from siblings, the sibling tools (monitor_processes, validate_security, plan_workflow) serve obviously different purposes, so no ambiguity arises.

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 does not mention prerequisites, exclusions, or scenarios where another tool would be more appropriate. For a command execution tool, this lack of context leaves the agent without clear selection criteria.

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