nft_check_ownership_token_id

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

No annotations are provided, so the description bears full responsibility. It only says 'Returns ownership status' but does not disclose whether the operation is read-only, has side effects, or any constraints like rate limits. This is minimal transparency.

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?

Four concise sentences: one states purpose, one lists required parameters, and one describes output. No wasted words; front-loaded with use case.

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?

No output schema exists, but the description only says 'Returns ownership status' without detailing the format (e.g., boolean, object). With 4 required params and no output schema, a bit more information about the return value would improve completeness.

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%, so baseline is 3. The description merely restates parameter names and uses without adding substantial meaning beyond what the schema already provides.

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 'verify ownership of a specific token (ERC-721 or ERC-1155) within a collection,' using a specific verb and resource. It distinguishes from sibling 'nft_check_ownership' by specifying token ID.

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?

Provides clear context for when to use (verify ownership of specific token) and lists all required parameters. However, it does not mention alternatives or exclusions, such as when to use the sibling tool 'nft_check_ownership'.

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