transfer_nft

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

No annotations are provided, so the description carries the full burden. It states the action but gives no details about private key usage, transaction signing, gas costs, ownership verification, or failure modes. For a state-changing operation, this is 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 that is clear, front-loaded, and free of fluff. Every word contributes to conveying the core action.

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?

This transfer tool has five parameters, including a sensitive privateKey, and no output schema. The description does not explain transaction signing, network implications, or what happens after transfer. It is too minimal for such a consequential operation.

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 has 100% coverage with meaningful descriptions for all five parameters, including a security note for privateKey. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 'Transfer' and clearly identifies the resource ('an NFT') and recipient ('to an address'). It states the action unambiguously but does not distinguish from sibling tools like batch_transfer_nfts or transfer_erc1155.

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. It does not mention that batch_transfer_nfts is for multiple NFTs, that transfer_erc1155 handles a different token standard, or that this tool requires the caller to be the NFT owner.

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