Execute Sudo Command

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

The description adds the policy constraint beyond the annotations (destructiveHint true). It does not elaborate on specific behaviors like return values or potential side effects, but the output schema exists and annotations cover the destructive nature, so the description is adequate.

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 front-loads the action and key constraint, with no wasted words.

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 destructive tool with 4 parameters and an output schema, the description covers the essential policy constraint but could be more complete with additional safety considerations or typical usage scenarios.

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 has 100% coverage for parameter descriptions, so the description does not add additional meaning beyond what the schema already provides, yielding a baseline score of 3.

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 action (execute command with sudo) and the resource (command with sudo privileges), and it distinguishes from sibling tools like proc_exec (without sudo) by mentioning the policy constraint.

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 clear context by noting the policy requirement 'only when allowRawSudo policy permits it', implying when the tool should be used. However, it does not explicitly state when not to use or compare to alternatives like proc_exec_stream.

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