ssh_execute_sudo

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

With no annotations, the description fully bears the burden of behavioral disclosure. It minimally indicates privilege escalation ('with sudo') but omits critical details: password masking behavior (though schema mentions it), potential side effects, security implications, and error handling. The description is insufficient for a sensitive operation.

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 sentence that efficiently conveys the core purpose. It is front-loaded with the action and context, but could include more necessary information without becoming verbose.

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 sensitivity (sudo execution), five parameters, and absence of both annotations and an output schema, the description is incomplete. It fails to explain return values (stdout, stderr, exit code), error behavior, or any confirmation prompts, leaving significant gaps for an AI agent.

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 with descriptions for all five parameters, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides; it does not clarify parameter interactions or usage nuances.

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 a command) and the specific context (with sudo on a remote server), effectively distinguishing it from the sibling tool 'ssh_execute'. However, it does not explicitly call out this differentiation or elaborate on the scope.

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 no guidance on when to use this tool versus alternatives like ssh_execute, nor does it mention prerequisites (e.g., sudo access, password requirements) or when not to use it. This leaves the agent to infer usage context.

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