check_nft_approval

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the purpose and does not explain what 'approved to manage NFTs' means (e.g., ERC721 setApprovalForAll vs token-level approval), whether it checks both, or what the return value indicates. The absence of any behavioral detail is a significant gap.

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 concise sentence of ten words with no filler or redundant information. It is front-loaded with the core action, making it easy to parse, though it sacrifices depth for brevity.

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?

Given the tool's moderate complexity (NFT approval concepts) and lack of an output schema, the description is incomplete. It does not explain what a positive result means, how the underlying approval standard works, or what parameters like tokenId imply. The schema partially clarifies, but the description alone leaves the agent without enough context to fully understand the tool's behavior.

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%, with all five parameters described in the input schema. The tool description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 applies; it does not compensate for any gaps.

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 ('Check') and resource ('operator approved to manage NFTs'), making the core function clear. It distinguishes itself from sibling tools like approve_nft_for_marketplace and revoke_nft_approval, though it could be more explicit about whether it covers both collection-wide and per-token approvals.

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. Sibling tools like check_nft_ownership and approve_nft_for_marketplace exist, and the description does not explain how this check differs or when it is appropriate to invoke it.

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