Get Asset By Symbol

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses meaningful behavior: symbols are uppercased before lookup, base units like GBYTE and MBYTE resolve specially, and the network defaults to mainnet. This materially helps an agent predict behavior.

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 compact and well-structured: core behavior first, then network guidance in a separate paragraph. Each sentence adds necessary information without 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?

The description handles the most important ambiguity—dual network support—and documents the default, but it omits semantics for the optional token_registry_address parameter and any information about return values or error cases. This is adequate for simple calls but not fully complete for the full parameter set.

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 0%, so the description must compensate. It explains the 'symbol' semantics (uppercasing and base aliases) and the 'network' enum/default, but never explains 'token_registry_address' beyond the vague phrase 'selected registry'. Partial compensation with a notable gap.

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?

Description states a specific operation: resolving a token symbol to an Obyte asset id via a registry. It clearly differentiates the tool from the reverse lookup sibling obyte_get_symbol_by_asset by naming the direction of resolution.

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?

Provides explicit invocation context: how to choose between mainnet and testnet, the default behavior, and an explicit instruction to confirm the network when the user hasn't specified one. It does not explicitly mention sibling alternatives, but the usage conditions for this tool are clear.

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