ssh_redpitaya_exec

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 usefully discloses the return contract (stdout/stderr/exit code) and that execution is remote and arbitrary, implying unbounded side effects. It omits credential/auth requirements (password vs. key_filename), timeout defaults, and any destructive-risk warning for running arbitrary commands on a live device.

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?

Two tight sentences that front-load the action and target before the usage examples. Every clause adds information and there is no filler.

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 an 8-parameter remote-execution tool with no annotations and no output schema, the description covers purpose and return values but leaves the credential/connection surface undocumented. An agent must inspect the raw schema to know how to authenticate, which is a meaningful gap for a high-risk tool.

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 only 25% — only command and exec_timeout are documented. The description adds no meaning for the six undocumented parameters (host, port, user, password, key_filename, connect_timeout), leaving authentication and connection semantics entirely to the agent's inference.

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 gives a specific verb (Run), resource (arbitrary shell command), and transport target (a Red Pitaya over SSH), plus the return shape (stdout/stderr/exit code). This clearly separates it from sibling tools like deploy_to_redpitaya or rp_build_project, though it never names a sibling to reinforce the distinction.

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?

It lists concrete example uses (status checks, dmesg reads, manual loader invocations), which implies when the tool is appropriate. However, there is no explicit when-not guidance or named alternative for cases where a dedicated sibling tool should be preferred.

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