Metaplex-nft Verify Collection

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

Annotations indicate this is a write operation (readOnlyHint=false) and the description mentions 'operation class write', which is consistent. However, it does not detail what on-chain state changes occur (e.g., marking the NFT as verified), potential side effects, or error conditions. The pre-checks list adds some context but lacks specificity.

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 verbose and includes irrelevant details about SAP MCP context, agent identity planning, and references to other tools. The core purpose is stated in the first sentence, but the rest is cluttered with extraneous information that reduces clarity and focus.

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?

With an output schema present, return values need not be explained. The description mentions prerequisites like confirming metadata URI and ownership, but does not cover all essential context (e.g., that the collectionAuthority must be the authority of the collection). The tool is part of a large set of siblings, and the description could be more tailored to its specific role.

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?

All three parameters (mint, collection, collectionAuthority) are described in the input schema with full coverage. The description does not provide additional semantic meaning or usage hints beyond the schema, so it adds no extra value. Baseline of 3 is appropriate.

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 starts with 'Verify an NFT as part of a collection' which clearly states the primary action. However, it does not differentiate from sibling tools like verifyCreator or setAndVerifyCollection, as it lists multiple workflows (collection, mint, metadata, etc.) without distinguishing this tool's specific role.

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 on when to use this tool versus alternatives. The description lists pre-checks (confirm metadata URI, collection mint, etc.) but does not specify conditions for using this tool or when another Metaplex tool would be more appropriate. Sibling tools with similar functions exist without mention.

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