Check if a tx was a USDC payment to TensorFeed

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

The description indicates a read-only on-chain lookup but does not explicitly state it has no side effects or require permissions. It also doesn't describe behavior for non-payment transactions.

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 concise sentences with key information front-loaded. No unnecessary words; each sentence adds value.

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?

Covers the main purpose, target, chain, and follow-up action. Lacks specifics on return structure, but acceptable for a simple tool without output schema.

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 schema already describes the tx_hash format. The description adds meaningful context about the target wallet and chain, which helps the agent understand the parameter's role beyond syntax.

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 checks if a transaction hash is a USDC payment to a specific wallet on Base mainnet, distinguishing it from sibling tools like usdc_balance or usdc_recent_payments_to.

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?

Implied usage for verifying a specific tx hash, but no explicit when-to-use or when-not-to-use compared to alternatives. The follow-up API call is mentioned but not as a usage guideline.

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