1s_nft_owner_live

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

The description discloses that the tool makes an RPC call (ownerOf) and works only for ERC721. However, it does not detail behavior on errors (e.g., nonexistent token, non-ERC721 contract), idempotency, or rate limits. With no annotations, the description partially covers transparency but leaves gaps.

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 extremely concise: two sentences with no unnecessary words. It front-loads the key action and adds the critical limitation in the second sentence.

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 description lacks information about the return value (expected to be an address) and does not mention default network behavior (network parameter is not required, but no default is stated). Error handling is not addressed. For a simple tool, this is adequate but incomplete.

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% description coverage, so each parameter is already well-defined. The tool description adds only that the call uses tokenId, which is redundant. Baseline 3 applies; no additional semantic value beyond schema.

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 tool's purpose: 'Get the current NFT owner via ownerOf(tokenId) RPC call.' It specifies the supported standard (ERC721), which distinguishes it from similar tools like 1s_erc1155_balance_live or 1s_nft_metadata_live.

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 explicit guidance on when to use this tool versus alternatives (e.g., 1s_erc721_tokens_live). It only mentions the ERC721 constraint, which is a limitation but not usage advice. No mention of prerequisites or when not to use.

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