sui_cli

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

No annotations provided; description lacks warnings about potential destructive actions or permissions required for arbitrary CLI commands. Minimal disclosure of behavioral traits beyond the basic 'run' action.

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?

Single sentence with examples is concise and efficient. Could organize as bullet list, but not necessary.

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?

No output schema; description omits return values (stdout/stderr) and error behavior. For a CLI wrapper with no annotations, this is insufficient for safe usage.

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%, so baseline is 3. Description adds examples but no extra semantics beyond schema descriptions of 'args' and 'cwd'.

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 defines the tool as executing 'any Sui CLI command', with examples ('client gas', 'move build') that distinguish it from sibling tools (e.g., sui_decompile, sui_move_build) which are specialized.

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?

Examples imply usage for commands not covered by siblings, but no explicit when-to-use, when-not-to-use, or alternatives provided. Agent must infer context.

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