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

With no annotations, the description carries the full transparency burden. It discloses a key behavioral trait: credits are escrowed and the platform settles the BTC payout later, indicating a delayed process. This adds real value beyond the basic action, though it does not mention reversibility or failure conditions.

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 sentences, front-loaded with the action, no redundant words. The escrow/settlement detail earns its place by adding behavioral context. Perfectly concise.

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 financial tool with no annotations, no output schema, and 0% parameter coverage, this description is too thin. It explains the basic flow but omits critical usage details like what paymentDetails is for, why btcAddress is optional, and what the platform does after escrow. The agent would likely need external knowledge to invoke this 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 description coverage is 0%, and the description provides no parameter-specific information. The names creditAmount, btcAddress, and paymentDetails are self-referential, but the description does not clarify their roles or the optional nature of btcAddress. The mention of 'earned credits' only hints at creditAmount, leaving other parameters unexplained.

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 ('Request') and resource ('Bitcoin cashout of earned credits'), clearly distinguishing this from sibling tools like wallet or buy_credits. It also adds context about escrowing and settlement, making the purpose unambiguous.

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 implies use when you have earned credits and want a BTC payout. It does not explicitly name alternatives or exclusions, but the context is clear enough to infer when to use it versus other financial tools. No explicit when-not guidance is given, but the purpose is specific.

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