tx_raw_hex_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read operation returning raw hex, but lacks details on error handling, size limitations, or idempotency. Basic behavioral info is present but could be more comprehensive.

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 uses two concise sentences with no extraneous information. It is front-loaded with the action verb 'Get' and the resource 'raw hexadecimal representation', making it efficient and easy to parse.

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 tool's simplicity (one parameter, no output schema) and the presence of sibling tools, the description adequately explains what the tool returns. However, it could be more complete by noting the return format (a hex string) and the length of the txid.

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 input schema has 0% coverage (no parameter descriptions) and the description only mentions the transaction ID generically. It does not specify the expected format (e.g., 64-character hex string) or provide any validation hints, adding minimal value 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?

The description clearly states the tool retrieves the raw hexadecimal representation of a Bitcoin transaction by its transaction ID. It specifies 'complete serialized transaction data in hexadecimal format', distinguishing it from sibling tools that return decoded or other formats.

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 provides no guidance on when to use this tool versus alternatives like transaction_get or tx_raw_decoded_get. No explicit context or use cases are given, leaving the agent to infer that it's for raw hex retrieval.

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