ssh_execute_sudo

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

No annotations are provided, so the description carries the full burden. It reveals that execution is privileged (sudo) on a remote host, but says nothing about sudo password handling, whether credentials must be pre-cached, failure/error behavior, or that this performs arbitrary mutation on a remote machine — a significant gap for a high-privilege 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?

A single, front-loaded sentence with no filler, which is structurally clean. But the brevity is under-specification rather than discipline: the same one sentence could have carried the sudo/credential caveat that the agent actually needs.

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 explained. But for a privileged remote-execution tool with zero annotations and zero parameter documentation, the description omits credential prerequisites, safety/risk posture, and any differentiation from the several overlapping ssh/execute siblings — insufficient for correct selection.

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%: neither 'hostname' nor 'command' has any description. The description adds no meaning beyond what the bare property names convey — no format hints (FQDN vs alias, shell syntax, multi-command support, quoting) to compensate for the coverage gap.

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 (execute) plus resource (command) and the distinguishing qualifier 'with sudo on remote Linux host', which separates it from ssh_execute_ssh. However, it never mentions the near-duplicate sibling execute_sudo, so the agent cannot tell those two apart from the description alone.

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?

There is no explicit when-to-use guidance, no prerequisites, and no exclusions. The agent must infer that sudo is required from the name, and cannot know whether credentials must first be set up via ssh_setup_credentials/cache_credentials or when to prefer execute_sudo or ssh_execute_ssh.

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