Execute Command (sudo)

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

No annotations are provided, so the description must disclose behavioral traits. It does mention the use of passwordless sudo (sudo -n), which is a helpful detail. However, it fails to disclose important traits such as that it runs arbitrary commands with elevated privileges, potential side effects, or the role of the confirm_code parameter. The description is too sparse for a potentially dangerous 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 a single, concise sentence that immediately conveys the core functionality. It is front-loaded with the action and resource, and there is no redundant or filler content. Every word earns its place.

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 higher complexity (arbitrary command execution with sudo), the description is extremely minimal. It lacks information about return values, execution mode (sync vs async), safety considerations, and the confirm_code parameter. With no output schema and no annotations, the description does not provide enough context for an agent to use the tool correctly and safely.

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 0%, so the description must compensate. It does clarify 'command' and 'machine' through the phrase 'Execute a command on a machine', but it completely omits the 'confirm_code' parameter, leaving its purpose unexplained. With three parameters and only partial coverage, the description does not adequately compensate for the missing schema documentation.

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 executes a command on a machine using passwordless sudo. The verb 'execute' and resource 'command on a machine using passwordless sudo' are specific, and the mention of sudo -n distinguishes it from the non-sudo exec tool. However, it does not explicitly state whether execution is synchronous or asynchronous, leaving some ambiguity versus exec-async-sudo.

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 tool is for running commands with sudo privileges, which is the primary use case. However, it provides no explicit guidance on when to use this tool versus alternatives like exec-async-sudo or exec. No exclusions or alternative references are given, so the guidance is purely implied.

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