execute_sudo

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

With no annotations, the description carries the full burden, yet it only implies privilege escalation without saying whether credentials or a sudo password are required, whether commands can mutate or destroy state, or what happens on failure. 'Legacy compatibility' is the one piece of useful behavioral context, signaling this may be deprecated.

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?

A single front-loaded sentence with no padding, which is structurally sound. However, brevity here comes at the cost of under-specification for a privileged, annotation-free tool.

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?

An output schema exists, so return values need not be described, but the definition omits credential prerequisites, permission scope, and the relationship to the duplicate ssh_execute_sudo. For a sudo-level mutation tool with zero annotations, that is a substantial gap.

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 and does not: it says nothing about the format of 'hostname' (alias vs FQDN vs inventory name) or how 'command' is interpreted (shell, quoting, multi-line). Both required parameters are left semantically opaque.

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?

States a specific verb and resource ('Execute command with sudo on remote Linux host'), which separates it from the plain execute_ssh sibling. It does not distinguish itself from the near-identical ssh_execute_sudo, leaving the agent to guess which sudo executor is intended.

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?

'Legacy compatibility' faintly hints that a newer path is preferred, but no alternative tool is named and no condition for choosing this over ssh_execute_sudo or execute_ssh is given. The agent must infer everything about when to use it.

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