dero_get_transaction

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

Annotations declare readOnlyHint=true, and the description confirms it is a read operation. It adds details about the return format (confirmation status, block hash, optional decoded JSON) and output structure, providing useful context beyond annotations. No contradictions.

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 well-structured with sections for overview, when to call, input requirements, and output. It is front-loaded with the main purpose. While not extremely concise, each sentence adds necessary information, making it clear and organized.

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 no output schema, the description explains the output shape and fields. It also provides usage context and cross-references to other tools. For a simple tool with two parameters, the description is fairly complete and covers essential aspects.

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 coverage is 100% with two parameters. The description adds value by emphasizing that txs_hashes must be a non-empty array of 64-char hex strings and that decode_as_json should prefer 1 to get JSON-decoded fields. This provides guidance 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 'Fetch one or more transactions by hash via DERO.GetTransaction,' specifying the verb and resource. It distinguishes itself from sibling tools by focusing on transactions by hash and mentioning related tools like dero_get_sc for contract invocations. The output fields are also listed, adding specificity.

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 explicitly states 'when tracing a tx by hash' and suggests pairing with dero_get_sc. It provides critical input requirements. However, it does not explicitly mention when not to use this tool or list alternatives among siblings, though the context is quite clear.

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