Metaplex-nft Delegate Authority

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which are consistent with a write delegation. The description adds value by listing authority types and prerequisites, but lacks details on whether delegation is additive or replaces existing delegates, and whether the current authority remains valid.

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 paragraph mixing purpose, context, and a separate agent workflow. Some phrases like 'SAP MCP context...' are redundant given annotations. It could be more structured and 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?

Given the tool's simplicity (4 required params, output schema exists), the description covers usage context, prerequisites, and a high-level workflow for agent use. It lacks return value description, but output schema presumably covers that, so this is acceptable.

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%, with all four parameters described in the schema. The description merely lists the authority types already in the schema and the prerequisite fields, adding no new parameter-level insight beyond what the schema provides. Baseline score of 3 applies.

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 the verb 'Delegate' and the resource 'specific authority', listing the four types (update, mint, freeze, collection). It distinguishes from sibling tools like revokeAuthority and verifyCreator by specifying the action and scope.

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 provides explicit when-to-use context ('Use for Metaplex NFT collection... workflows') and prerequisites ('Confirm metadata URI... before writes'). It also outlines related tool sequence for agent identity, but does not explicitly contrast with alternative delegation tools.

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