run_commands

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

With no annotations provided, the description must carry the burden of disclosing behavioral traits. It mentions 'enable-mode' indicating a required privilege level and 'labelled output' indicating response format, but it does not disclose potential side effects of running commands, error handling, session behavior, or any prerequisites. This is insufficient transparency for a command execution tool.

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, well-structured sentence that is front-loaded with the primary action and scope. It is concise with no filler words, every word adding value, and perfectly sized for a straightforward command execution tool.

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?

Despite the presence of an output schema (which may cover return values), the overall description is incomplete for a tool with no annotations and no parameter documentation. It lacks safety warnings, prerequisite context, and guidance on when to use this tool versus siblings. A command execution tool should provide more context about enable mode requirements and potential impacts.

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%, and the description does not mention any parameters by name or provide semantics beyond implying 'commands' and 'hostname' through the phrase 'multiple commands on one EOS device'. The config_path parameter is completely unexplained. The description fails to compensate for the lack of schema descriptions.

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 tool's function: 'Run multiple enable-mode commands on one EOS device and return labelled output.' It specifies the verb (run), resource (multiple enable-mode commands on one EOS device), and output format (labelled output), distinguishing it from sibling tools like run_command (single command) and run_commands_batch (likely multiple devices).

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 implies usage for multiple commands on a single device, but it does not explicitly state when to prefer this tool over alternatives such as run_command or run_commands_batch. There is no mention of exclusions or alternative selection guidance, so the usage context is only implied.

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