check_nft_ownership

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

With no annotations provided, the description must disclose behavior. It does not state return type, whether the operation is read-only, or how the missing address parameter is resolved. The mismatch between the description's 'address' and the schema's lack of an address parameter also undermines behavioral 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?

The description is concise (one sentence) and front-loaded, with no wasted words. However, its brevity omits critical information about the address ambiguity, making it under-specifying rather than helpfully concise.

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 tool has no output schema, no annotations, and a misleading description. The critical omission of an address parameter means an agent cannot correctly invoke the tool as described. The tool is incomplete and likely unusable without additional context.

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 all parameters (100% description coverage), but the description actively misleads by referencing an 'address' that doesn't exist in the schema. This adds negative value beyond the schema, as it could cause an agent to search for a nonexistent parameter.

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 states a clear action ('Check if an address owns a specific NFT'), but it mentions an 'address' that is not present in the input schema (which only accepts collectionAddress, tokenId, and network). This creates confusion about which address's ownership is being checked, making the purpose misleading relative to the actual parameters.

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 vs. alternatives like get_nfts_by_owner or check_nft_approval. The description also fails to explain how to specify the owner address, which is essential for usage and is not addressed by the schema.

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