What owning this actually means

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds valuable behavioral detail: data is 'decoded from raw bytes, no indexer,' collection-level plugins are read and 'marked inherited,' and the read is purely read-only. This gives an agent accurate expectations about data sourcing and coverage without contradicting the annotations.

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 dense but every sentence earns its place: purpose, concrete facts, collection inheritance nuance, marketplace contrast, use cases, and data-source caveat. The most important purpose statement is front-loaded, and there is no filler or repetition.

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 single-parameter read tool with no output schema, the description covers what the tool does, what questions it answers, how it handles collection-level plugins, when to use it, and the raw-bytes/no-indexer caveat. An agent has enough context to invoke it correctly and interpret its high-level purpose.

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?

The schema already documents the only parameter, mint, as 'Metaplex Core asset address,' giving 100% schema description coverage. The tool description reinforces that the asset is a Metaplex Core asset but does not add meaningful syntactic or semantic details beyond the schema, so the baseline score 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 opens with a specific verb and resource: 'Decode the Metaplex Core plugins on an asset and translate them into custody facts.' It then enumerates concrete questions the tool answers (delegates, frozen state, royalties, metadata mutability, serial authenticity), and distinguishes itself from marketplaces that show only picture and price. This clearly differentiates it from siblings like get_asset and explain_mechanics.

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 gives explicit when-to-use triggers: 'Use before a purchase, when a listing "cannot transfer", or when someone asks whether a pack burns on open.' It also hints at a contrast with marketplaces, but does not name alternative sibling tools or provide explicit when-not-to-use exclusions, so it falls just short of a 5.

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