Metaplex-nft Configure Royalties

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

Annotations indicate write, non-destructive, non-idempotent. The description adds 'operation class write' and mentions confirmation before writes, but does not disclose side effects (e.g., whether existing royalties are overwritten or merged). It provides adequate context beyond annotations but lacks depth.

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, including tangential SAP context, agent identity planning, and unrelated workflows. It is not front-loaded; the core purpose is buried. Every sentence does not earn its place, reducing efficiency for an AI agent.

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 tool is simple (configure royalties), and an output schema exists. However, the description includes extraneous information and omits specifics about the update process. It is complete enough for basic understanding but lacks focus on the tool's core 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 coverage is 100%; each parameter has a clear description. The description adds no new semantic information beyond the schema, only generic prerequisites. Baseline 3 is appropriate as the schema already documents parameters well.

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 'Configure royalty fee and creator splits for an NFT', which is a specific verb-resource pairing. It clearly identifies the tool's primary function. While sibling tools exist (e.g., metaplex-nft_updateMetadata), the description does not explicitly differentiate, but the focus on royalties is distinct.

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 lists prerequisites ('Confirm metadata URI...') but does not specify when to use this tool versus alternatives. It mentions 'Use for Metaplex NFT collection, mint, metadata... workflows' which is too broad and does not guide selection. No explicit when-not-to-use or alternative tools are referenced.

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