iota_wallet_reject

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

No annotations are provided, so the description alone must disclose behavioral traits. It only states 'Reject' without detailing side effects, reversibility, or whether it permanently removes the transaction. It doesn't mention if rejection requires confirmation or what happens to the wallet state, leaving significant behavioral unknowns for the agent.

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, front-loaded sentence with no unnecessary words. It efficiently states the action and target, making it easy to parse. Conciseness is excellent.

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 simple tool with one required parameter and full schema coverage, the description is largely sufficient. It clearly defines the action and scope. However, it lacks some contextual depth like behavior on non-pending transactions or return value details, but given the tool's simplicity, this is not a major gap.

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 input schema covers 100% of parameter semantics with the requestId description 'Request ID to reject'. The tool description adds no extra meaning beyond the schema, so the baseline of 3 is appropriate given the schema's completeness.

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 'Reject a pending transaction' uses a specific verb ('reject') and a clear resource ('pending transaction'). It clearly distinguishes from sibling tools like iota_wallet_approve, which handles the opposite action, and iota_wallet_pending, which likely lists pending transactions.

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 implies the tool is for pending transactions but provides no explicit guidance on when to use it versus alternatives. It does not mention that this should be used only after reviewing pending transactions via iota_wallet_pending, nor does it exclude cases like already-approved transactions. Usage context is implied but not detailed.

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