Src20 Tx

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

With no annotations, the description carries the behavioral burden. 'Decode' suggests a safe, read-only operation and the field list clarifies what is returned, but it does not disclose behavior for missing or malformed hashes, validity semantics, or any side effects. Adequate for a simple lookup, but not richly transparent.

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 front-loads the action and resource, then efficiently lists the decoded fields after a colon. There is no redundancy or filler, so every word contributes to understanding the tool.

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 simple single-parameter schema and the presence of an output schema, the description is complete enough: it identifies the input, the operation, and the key result fields. It does not need to explain return values further because the output schema covers structure.

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 has no parameter descriptions, but the description clarifies that tx_hash is the Bitcoin transaction hash used to decode the SRC-20 transaction. This adds real meaning beyond the bare parameter name, even though it does not specify format details like hex length.

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 uses a specific verb ('Decode') and a clear resource ('one SRC-20 transaction') with the lookup key ('by its Bitcoin tx hash'). It also lists the returned fields, which makes the tool's purpose unmistakable and distinguishes it from sibling tools like src20_transactions or src20_balance.

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 guidance is given about when to prefer this tool over alternatives or when not to use it. The description implies a hash-lookup use case but never states it explicitly or names sibling tools that might be more appropriate for listing or searching.

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