Execute Run:AI CLI

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

With no annotations, the description carries the full burden for behavioral disclosure. It adds useful context like local session, port-forward tunneling, streaming logs, and --follow, but omits safety considerations, permissions, return value format, and error behavior for an execution tool that can run arbitrary commands inside containers.

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?

Two focused sentences: purpose comes first, followed by supported subcommands and an explicit pointer to sibling tools for other operations. No filler or repetition.

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?

The description is strong on purpose and usage, but the tool is a CLI execution tool with no output schema, and the description does not mention return output, error handling, or exit behavior. That gap matters for invocation correctness. However, the supported-command scoping and API alternative guidance make it minimally viable.

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 covers 100% of parameters, so baseline is 3. The description adds value by narrowing command_args to the allowed subcommands and giving concrete examples (nvidia-smi, bash, --follow). timeout_seconds is clarified in the schema with 'Use 0 for port-forward', but the description itself doesn't add timeout guidance beyond the schema.

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?

Description clearly states it executes Run:AI CLI local session operations and enumerates specific subcommands (port-forward, exec, attach, logs, diagnostics). It also explicitly distinguishes from siblings like search_runai_api_spec and call_runai_api by limiting scope to API-irreplaceable tasks.

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?

Provides explicit guidance: 'API 대체 불가능한 작업만' (only tasks that cannot be replaced by API) and lists exactly when to use each subcommand. It also says to use search_runai_api_spec + call_runai_api for workload create/delete/query, naming alternatives clearly.

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