emblem: emblemResolveAsset

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds workflow context: this tool must be called before vault creation. This additional behavioral insight goes beyond 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 two sentences: the first states the function, the second emphasizes critical usage. No filler words, front-loaded with purpose. Perfectly 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 (one parameter, read-only), the description is largely complete. It does not describe the output format, but that is acceptable given the tool's straightforward nature and the presence of sibling tools that may clarify collections.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by including examples of asset names (e.g., 'TESTNETPEPE'), which aids agent understanding beyond the schema text.

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 tool's function: 'Resolve an asset name to its curated collection.' It specifies the verb (resolve), resource (asset name), and output (curated collection). The mention 'CRITICAL: Call this BEFORE emblemCreateVault' differentiates it from sibling tools that deal with collections or vaults.

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 explicitly guides when to use this tool: 'Call this BEFORE emblemCreateVault when vaulting user assets to find the correct collection name.' It provides a critical ordering dependency, which is excellent usage guidance.

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