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

Beyond the annotations, the description discloses critical behavioral nuances: the tool returns instructions rather than executing a transfer, never claims success before reconciliation, and prefers x402 when enabled. This adds meaningful context about async settlement and ownership constraints, which is not available from annotations alone.

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: three sentences covering purpose, payment method, and settlement behavior. It is front-loaded with the core function and contains no redundant filler.

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 output schema and annotations, the description covers all essential aspects: what it returns (funding instructions), the precondition (draft ownership), the payment routing behavior, and the reconciliation safeguard. No critical information is missing for an agent to select and invoke the 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?

The schema description covers idempotency_key well, but research_bounty_id lacks a description. The tool description partially compensates by explaining that the ID must refer to a draft created by the same key, adding ownership context. However, it does not elaborate on format or relationship to other IDs, so it adds moderate value 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 uses a specific verb ('Return') and resource ('owner-bound Base/USDC funding instructions') tied to a clear precondition ('draft created by this same Bearer agent key'). It distinguishes from sibling tools like get_funding_quote or create_bounty_draft by focusing on funding instructions rather than quotes or creation.

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?

The description provides clear usage context: it is only for drafts created by the same agent key, which implicitly rules out other scenarios. It also mentions payment method selection (x402 preferred, Stripe fallback), giving guidance on how to proceed. However, it does not explicitly reference alternative tools or state when not to use, so it stops short of a 5.

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