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 only says the tool executes a shell command, but omits critical traits: whether the command can mutate the filesystem, install packages, access the network, time out, or how output and exit codes are returned. For an arbitrary command executor, this is a significant transparency gap.

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, front-loaded sentence with no filler. It conveys the core operation efficiently, though the extreme brevity comes at the cost of behavioral context that other dimensions penalize.

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?

Despite a simple one-parameter schema, this is a powerful tool with potentially wide-ranging effects. The description lacks essential context about return values (stdout/stderr, exit status), side effects, and sandbox restrictions, and there is no output schema to compensate. An agent has enough to guess the call shape but not enough to anticipate the tool's behavior.

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% for the single 'command' parameter, and its description ('The shell command to execute') already conveys the parameter's meaning. The tool description adds no further nuance about command syntax, allowed shells, or working directory, so it neither improves nor worsens the baseline.

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 ('Execute') on a defined resource ('shell command') within a bounded environment ('sandbox'). It is distinguishable from the sibling execute_code, which implies code execution rather than shell commands, though it doesn't explicitly name the sibling as an alternative.

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?

No guidance is given about when to use execute_command versus execute_code or other file/session tools. There are no eligibility criteria, no exclusions, and no mention of prerequisites such as an active session, leaving an agent to infer usage from the name alone.

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