arc200_get_metadata

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

No annotations are provided, so the description must disclose behavior. It indicates a read operation and mentions 'ulujs + simulation', hinting at simulation-based execution, but does not detail return format, error conditions, or non-mutating guarantees beyond the verb 'Read'.

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?

One concise sentence that front-loads the core purpose and lists return fields. The only extra descriptor 'ulujs + simulation' is compact but potentially cryptic.

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?

Description lists the return fields (name, symbol, decimals, totalSupply), which is helpful given there is no output schema. However, it lacks context about the simulation behavior and does not address error cases or prerequisites, leaving some gaps.

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 already provides 100% description coverage for both network and appId parameters. The tool description adds no parameter-specific details beyond the schema.

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 clearly states 'Read ARC-200 name, symbol, decimals, and totalSupply', specifying a verb, resource, and exact data fields. The mention of ARC-200 distinguishes it from sibling arc72_get_metadata.

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?

No explicit when-to-use or alternative guidance provided. The tool's purpose implies it is for retrieving standard token metadata, but it does not contrast with balance or allowance tools.

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