sui_move_publish_unsigned

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

The description accurately states the function (generate unsigned bytes) which implies no immediate state change, but it does not detail any permissions, side effects, or error conditions. Given no annotations, a bit more context would be helpful.

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-loading the core action, and includes a critical workflow hint in a compact form. Every word is purposeful.

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 covers the core function and suggests a workflow, but it lacks details on output format, error scenarios, and preconditions. Given the absence of an output schema, more explanation of what the tool returns would improve completeness.

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?

Both parameters are described adequately in the schema with units and defaults. The tool description does not add additional semantic information beyond what the schema already provides, so it meets the baseline for high coverage.

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 action (generate unsigned transaction bytes) and the resource (publishing a Move package), and hints at a workflow with a sibling tool, making the purpose unambiguous.

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 provides a clear usage hint by mentioning the companion tool for signing, indicating a two-step workflow. However, it lacks explicit exclusions or alternatives.

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