execute_command

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions execution context ('current tracked directory') but doesn't disclose critical behavioral traits like security implications, permission requirements, error handling, timeout behavior, or whether commands run interactively. For a potentially dangerous shell execution tool, this leaves significant gaps in understanding its behavior.

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 perfectly concise with two sentences that each earn their place: the first states the core functionality, and the second adds important contextual constraint about execution directory. No wasted words, front-loaded with the main purpose.

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 this is a potentially dangerous shell execution tool with no annotations and no output schema, the description is incomplete. It doesn't explain what kind of output is returned (stdout? stderr? exit code?), error conditions, security warnings, or limitations. The context about current directory is helpful but insufficient for safe and effective use.

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% with the single 'command' parameter well-documented in the schema. The description adds no additional parameter semantics beyond what the schema provides about the command parameter. This meets the baseline expectation when schema coverage is complete.

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 shell command'), the target resource ('on the connected VPS'), and the outcome ('return the output'). It distinguishes itself from siblings like change_directory, list_directory, or read_file by focusing on arbitrary command execution rather than specific file operations.

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 implies usage context by mentioning 'connected VPS' and 'current tracked directory', suggesting it should be used after establishing a connection and potentially after navigating directories. However, it doesn't explicitly state when to use this versus alternatives like specific file operations (read_file, write_file) or when not to use it (e.g., for simple directory listing vs. using list_directory).

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