theta_get_transaction

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

No annotations provided; description declares read-only behavior, which is sufficient. However, lacks details on potential error conditions, authentication requirements, or network specificity (e.g., which chain).

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?

Two short sentences, no redundant information. However, could be more front-loaded with the single parameter note.

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 and simple structure, the description provides basics but misses return value expectations (e.g., what fields are in transaction details). Adequate for a straightforward fetch.

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%; the description does not elaborate on 'tx_hash' format, length, or examples. An agent might need to guess whether it's a hex string with 0x prefix or a hash 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?

Description clearly states verb 'Fetch' and resource 'transaction details by hash'. It distinguishes from sibling tools like 'theta_read_contract' and 'theta_get_balance' which operate on different resources. The 'Read-only' qualifier reinforces its purpose.

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 explicit guidance on when to use this tool vs siblings, but the purpose is self-evident given the unique resource (transaction hash). A brief note about not using for contract data would elevate it.

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