system

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: it does not say the command runs as arbitrary shell code under PyMOL's process user, that side effects are irreversible, or that it executes on the server machine rather than in the molecular session.

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?

One short sentence with no wasted words, but the brevity reflects under-specification rather than economy. Nothing is front-loaded beyond the raw action.

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 arbitrary-shell-execution tool flagged destructive and open-world, the definition omits the risk surface, execution environment, and the distinction from execute_pymol_command. An output schema exists, so return values need not be explained, but the missing safety and routing context leaves this inadequate.

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 coverage is 100% and the single "command" parameter is documented as a shell command run on the PyMOL machine. With the schema doing the work, the baseline of 3 applies; the description adds no syntax, quoting, or timeout semantics.

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?

"Executes a system command" states a verb and resource, but it is close to restating the bare tool name "system" and gives no scope on what kind of command (shell vs PyMOL). It also fails to distinguish this from the sibling execute_pymol_command, which an agent could easily confuse it with.

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 when-to-use guidance, no mention of when NOT to use it (e.g., in favor of execute_pymol_command for PyMOL commands), and no prerequisites such as required shell access or environment. The agent must infer all routing decisions.

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