decode_raw_transaction

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

Annotations already mark this as read-only and non-destructive. The description adds useful behavioral context: it works offline and focuses on showing destinations. It also clarifies the network parameter's role in address rendering, going beyond the schema's bare type information.

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 short and front-loaded with the core action and output. It includes only necessary details, with parameter explanations separated cleanly. Every sentence adds value and there is no repetition of schema fields.

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?

For a read-only decoder with an output schema present, the description covers the essential inputs and behavioral context. It does not explain error cases or exact network value formats, but these are not critical given the simple parameter list and output schema availability.

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 does: raw_tx is explained as 'the raw transaction hex' and network as 'Override the server's network for address rendering.' While brief, this provides meaningful semantics for both parameters.

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 and resource: 'Decode raw transaction hex, showing destinations.' It clearly identifies the input format and output focus, distinguishing it from sibling tools like decode_script, decode_wif, and decode_psbt.

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 states it 'Works offline,' which gives some context about when it is appropriate to use. However, it does not explicitly explain when to choose this over related decoders or mention any exclusions, leaving usage guidance mostly implied.

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