bsv_decodeTransaction

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

With no annotations provided, the description carries the full burden. It discloses behavioral traits such as supporting hex/base64 encoding, fetching on-chain data, and returning detailed insights, but lacks information on error handling, rate limits, or authentication needs, which are important for a tool with no annotation coverage.

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 appropriately sized and front-loaded, starting with the core purpose. Every sentence adds value, such as input formats and output details, but it could be slightly more streamlined by avoiding redundant phrases like 'powerful 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 complexity (1 parameter with nested objects, no output schema, and no annotations), the description is somewhat complete but lacks details on return values, error cases, or performance considerations. It covers input semantics well but falls short in fully compensating for the missing structured data.

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 description adds significant meaning beyond the input schema, which has 0% coverage. It explains that 'tx' can be a transaction ID or raw data and clarifies encoding options, effectively compensating for the schema's lack of descriptions. However, it doesn't detail the structure of 'args' or provide examples.

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 purpose with specific verbs ('decodes and analyzes') and resource ('Bitcoin SV transactions'), distinguishing it from siblings like price checking or ordinal tools. It specifies the comprehensive insights returned, making the function unambiguous.

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 implies usage by mentioning it accepts transaction IDs or raw data, but does not explicitly state when to use this tool versus alternatives like bsv_explore or other Bitcoin-related tools. No exclusions or clear alternatives are provided, leaving some ambiguity.

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