execute-command

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says commands are executed and output is returned; it fails to mention that this can run arbitrary, potentially destructive commands on the server, how timeouts or working directories affect execution, or what the output result contains (e.g., stdout, stderr, exit code).

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 efficient sentence that front-loads the core action and outcome with no redundant words. It is concise and well-structured, though it could have included more behavioral context without becoming bloated.

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?

For a powerful command-execution tool with four parameters and no output schema, the description is incomplete. It does not explain return values, failure modes, side effects, or how parameters like directory and connectionName influence execution. Given the potential for destructive commands, more context is necessary for safe and correct 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?

The input schema provides 100% description coverage for all four parameters, including default behavior for timeout and connectionName. The description text adds no additional parameter meaning, but the schema already documents each field adequately, so the baseline of 3 applies.

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 specific verb and resource: "Execute command on connected server and get output result." This clearly conveys the tool's action and outcome, and it is immediately distinguishable from the sibling tools (upload, download, list-servers, list-directory), which all perform different 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 this is for running shell commands on a server versus the file transfer and listing operations of sibling tools, but it provides no explicit when-to-use guidance, prerequisites, or exclusions. Usage context is inferable rather than stated.

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