iota_wallet_sign_execute

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

With no annotations, the description must carry the full burden of behavioral disclosure. It states 'Sign and execute' but fails to disclose the irreversible nature of executing a transaction, whether it waits for confirmation, what happens on failure, or any side effects. This is a mutation tool, and the description offers no safety or outcome details.

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 short sentence that is front-loaded and contains no filler. It is concise, though somewhat under-specified for a transaction-signing tool; however, that lack of detail is a completeness issue rather than a conciseness issue.

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 tool that signs and executes a transaction (a potentially irreversible action), the description is extremely inadequate. There is no output schema, no annotations, and no mention of success/failure behavior, confirmation, return values, or prerequisites. The description does not enable an agent to understand the tool's full behavior or consequences.

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 provides 100% coverage of the single parameter txBytes with a clear description ('Base64-encoded unsigned transaction bytes'). The description's parenthetical 'base64 tx bytes' adds no meaning beyond the schema, so the baseline score of 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 the action ('Sign and execute') and the resource ('a transaction'), which is specific and unambiguous. However, it does not explicitly distinguish itself from sibling tools like iota_wallet_approve/reject or iota_transaction, though the verb makes the purpose understandable.

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 tool versus alternatives such as iota_wallet_approve, iota_wallet_reject, or iota_cli. There is no mention of prerequisites, workflows, or conditions that indicate this is the appropriate tool.

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