iot_execute_command

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

With no annotations, the description alone must disclose behavior. It only states the action without revealing whether commands can modify device state, what privileges are used, how output is returned, or any timeouts/error handling. This is a significant gap 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, front-loaded sentence with no unnecessary words. It efficiently conveys the core purpose, earning a perfect score for conciseness and structure.

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 a potentially dangerous arbitrary-command execution tool with no output schema or annotations, the description is inadequate. It fails to mention return values, safety risks, authentication requirements, or how this tool fits among the numerous read-only sibling tools.

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 both parameters have basic descriptions. The description adds context that device_id refers to SSH-capable devices and command can be any CLI command for listed vendors, but it does not elaborate on command syntax, device_id format, or execution behavior. Baseline 3 is appropriate.

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 a specific verb ('Execute') and resource ('CLI command on any SSH-capable device'), listing example vendors. However, it does not distinguish itself from sibling tools like fortigate_execute_cli or mikrotik_execute_command, which serve similar purposes for specific vendors.

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?

No guidance is provided on when to use this generic executor versus vendor-specific execute_command tools or read-only inspection commands. There is no mention of prerequisites, safety restrictions, or alternative tools.

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