get_indexed_tx

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

No annotations provided. The verb 'Get' implies a read-only operation, but the description does not disclose error handling (e.g., behavior for missing hash), rate limits, or whether the transaction must be previously indexed. Minimal behavioral insight.

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?

Single sentence, no redundant words. Front-loaded with verb and resource. Every word earns its place.

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?

Simple tool with one parameter and no output schema. The description is minimally adequate but lacks details on return format, error states, or what 'indexed' implies. Meets baseline for a low-complexity tool.

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?

Input schema coverage is 100% with the single parameter 'tx_hash' described as 'Transaction hash'. The description adds no additional meaning beyond the schema. Baseline of 3 is appropriate since schema already documents the parameter sufficiently.

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-resource pair 'Get an indexed transaction', which clearly states the action and object. It distinguishes from the sibling 'get_transaction' by adding 'indexed', though the meaning of 'indexed' is not further explained, leaving slight ambiguity.

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 guidance on when to use this tool versus alternatives like 'get_transaction'. No mention of prerequisites, context, or exclusion criteria. The description only states what it does, not when to use it.

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