What owning this actually means

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

Annotations only cover readOnlyHint and openWorldHint; the description adds substantial context beyond them: decoded from raw bytes with no indexer, collection-level plugins are read and marked inherited, and it enumerates what each decoded fact means (permanent delegates normal on packs but a red flag on keepers, 'no rule checks that the fee is paid'). It also flags an interpretive nuance (advisory vs. enforcing royalty) that annotations cannot convey.

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?

Front-loaded with the core action and outcome, and the highest-value facts (delegate/burn power) appear first. It is dense with parentheticals and long, but most clauses carry distinct information rather than filler.

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?

For a read-only tool with no output schema, the description adequately previews what comes back by enumerating the custody dimensions it decodes and noting that collection-level plugins are included and marked inherited. It stops short of describing the return envelope or any pagination/scoping behavior, but nothing essential for correct invocation is missing.

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% for the single 'mint' parameter, so the schema already does the work. The description adds domain framing (a Metaplex Core asset) but no format or syntax detail beyond what the schema states, which is the expected baseline when the schema is self-sufficient.

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?

Specific verb (decode Metaplex Core plugins) applied to a specific resource (an asset), producing named outputs (custody facts: delegate powers, freeze state, royalty rule set, mutability, edition status). It explicitly contrasts itself with marketplaces ('Marketplaces show the picture and the price; this shows the rules attached to the account') and with sibling get_asset, so an agent can route correctly without opening schemas.

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?

Gives three concrete triggers: before a purchase, when a listing 'cannot transfer', or when asked whether a pack burns on open. Clear context for use, but it names no sibling tool as an explicit alternative, leaving the routing to be inferred from the marketplace contrast.

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