iota_cli

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

There are no annotations, so the description carries the full responsibility for behavioral disclosure. It states that it runs any CLI command but does not disclose potential side effects, safety implications, exit codes, or output format. For a tool that can execute arbitrary commands, this is a significant lack of transparency.

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 extremely concise, front-loaded with the action and resource, and includes illustrative examples. Every word earns its place, and there is no redundant information.

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 the tool's potential for arbitrary command execution and the absence of any output schema or annotations, the description is under-specified. It lacks safety warnings, expected return value structure, or guidance on how the tool interacts with the working directory. The medium complexity demands more context than a single line provides.

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?

The schema already documents both parameters (cwd and args) with 100% coverage, giving a baseline of 3. The description adds value by providing example argument values ('client gas', 'client ptb'), which illustrate the expected format and help an agent construct valid invocations, so a 4 is warranted.

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 purpose: running any IOTA CLI command, with concrete examples like 'client gas' and 'client objects'. The verb 'Run' and resource 'any IOTA CLI command' make it distinct from sibling tools that are specialized wrappers for specific IOTA operations.

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 CLI runner versus the many specific sibling tools (e.g., iota_wallet_balance, iota_get_coins). The description does not mention that specialized tools should be preferred when available, or any scenarios where this tool is the right choice.

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