api_algod_get_pending_transaction

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

No annotations are provided, so the description carries full burden. It states 'Get pending transaction information' which implies a read-only operation, but doesn't disclose any behavioral traits like authentication requirements, rate limits, error conditions, or what 'pending' specifically means in this context. The description is minimal and lacks operational context.

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 extremely concise at just four words, with zero wasted language. It's front-loaded with the core purpose. While it may be too brief for completeness, it earns full marks for conciseness.

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 complexity of transaction lookup in a blockchain context, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'pending transaction information' includes, how it differs from other transaction tools, or what the return format looks like. For a tool with one required parameter and two optional ones in a specialized domain, more context is needed.

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 100%, so the schema fully documents all three parameters (txId, network, itemsPerPage). The description doesn't add any parameter-specific context beyond what's in the schema. The baseline score of 3 reflects adequate parameter documentation through the schema alone.

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 'Get pending transaction information' clearly states the action (get) and resource (pending transaction information), but it's quite generic. It doesn't specify what kind of information is retrieved or differentiate meaningfully from sibling tools like 'api_algod_get_pending_transactions' (plural) or 'api_indexer_lookup_transaction_by_id'.

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 is provided on when to use this tool versus alternatives. With many sibling tools for transaction lookup (e.g., api_algod_get_pending_transactions, api_indexer_lookup_transaction_by_id), the description offers no context about whether this is for pending vs. confirmed transactions, Algod vs. Indexer APIs, or single vs. batch queries.

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