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

With annotations already indicating non-read-only and non-idempotent behavior, the description adds context by specifying it is a POST endpoint, verifies on-chain transfer, and returns a cross-redeemable token. It does not detail failure modes or rate limits, but the annotations cover the basic safety profile.

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?

Three concise sentences, each with a distinct purpose: what it does, when to use it, and what the result means. No redundant phrasing.

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?

For a tool with no output schema, the description fully covers the return value (token and credit count), the necessary context (tx hash and memo), and the post-verification usage (cross-redeemable). It is complete for an agent to use this tool correctly.

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%, but the description reinforces that both tx_hash and memo are expected in practice despite being schema-optional. It clarifies the workflow by linking the nonce to the memo from tf_payment_buy_credits, which adds operational nuance 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 the tool verifies a Base mainnet USDC transfer and returns a bearer token plus credit count. It names the specific token format (tf_live_<64-char-hex>) and distinguishes this from sibling payment tools like tf_payment_buy_credits or tf_payment_balance.

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?

Explicitly says 'Use after the agent has sent USDC' and directs the agent to provide the tx hash and memo from tf_payment_buy_credits. This establishes a clear workflow and timing, making it obvious when this tool should be invoked relative to its siblings.

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