exec_cmd

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

There are no annotations, so the description carries the full transparency burden. It clearly discloses that the tool runs arbitrary shell commands, is not vetted by any whitelist, and should be used cautiously. It does not mention every possible side effect, but for a generic exec tool the core risk profile is explicit.

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 two short sentences, front-loads the core capability, provides usage examples, and then adds the important safety warning. There is no filler or duplicated schema content.

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 a one-parameter schema and the existence of an output schema, the description is operationally complete: it specifies the execution location, command generality, intended use, and no-whitelist risk. Nothing else is necessary for correct invocation.

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%, yet the description fully compensates for the single parameter: command is explained as '任意 shell 命令' and supported with concrete examples like rostopic pub and catkin_make. For a one-parameter tool, this is complete semantic guidance.

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 states a specific verb, resource, and scope: execute arbitrary shell commands inside the container. It also labels the tool as a general fallback, which makes its role immediately distinguishable from sibling status/inspection tools and from ssh_exec.

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 gives concrete usage signals with examples such as rostopic pub and catkin_make, and calls itself a fallback tool used for temporary operations. It implicitly says to prefer dedicated tools first, but it does not explicitly name alternatives or exclusions.

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