nft_approve

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention that this is an on-chain state-changing operation that may require a wallet connection, gas fees, or that it updates the NFT's operator approval. The phrase 'approve' hints at permission but does not disclose side effects or prerequisites.

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, focused sentence of 10 words. It is immediately clear and contains no redundant or speculative content, earning full marks for conciseness.

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?

As a mutation tool with no annotations and no output schema, the description should clarify the on-chain effect and likely return value (e.g., transaction hash). It also omits important context such as ownership requirements and the typical approval-before-transfer flow. The tool may be simple, but the description remains under-specified for safe agent invocation.

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 description coverage is 100%—each parameter (tokenId, operator, contractAddress) has a clear description. The tool description adds no new semantic information beyond referring to 'another address' and 'specific NFT,' which the schema already covers. Baseline 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 uses a specific verb ('Approve'), identifies the resource (a specific NFT), and states the beneficiary (another address). This clearly distinguishes it from sibling tools like nft_transfer (which actually moves the NFT) and nft_mint (which creates one).

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 no guidance on when to use this tool versus alternatives, nor does it mention typical workflow prerequisites (e.g., that approval is often a prerequisite for a transfer by another address). It simply states what it does without any contextual usage hints.

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