iota_wallet_approve

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

No annotations are available, so the description carries the full burden of disclosing behavioral traits. It only says 'Approve a pending transaction' without explaining side effects (e.g., whether approval triggers submission, is irreversible, or requires additional confirmation). This is a mutating wallet operation with zero additional context, which is severely insufficient.

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 sentence with no filler and front-loads the purpose. It is appropriately terse for a simple tool, though it sacrifices behavioral clarity. It earns its place as a concise statement of intent.

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 tool is a mutating wallet operation with no annotations, no output schema, and a single parameter. The description fails to explain what happens after approval, any preconditions, or the result of the operation. This incomplete context leaves an AI agent uncertain about the tool's full impact.

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 covers 100% of the parameters, with 'requestId' described as 'Request ID to approve'. The description adds nothing beyond the schema, so the baseline score of 3 applies given the high schema 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 (approve) and the object (a pending transaction). It distinguishes from siblings like iota_wallet_reject, though it does not explicitly name alternatives. The verb+resource structure is specific enough for basic understanding.

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. There is no mention of prerequisites, such as first listing pending transactions with iota_wallet_pending, or contrasting with iota_wallet_reject. The context for when approval is appropriate is absent.

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