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

Annotations already mark it as non-read-only and destructive, but the description adds 'Escrows gas; operator pays BTC manually,' revealing the escrow mechanism and human-operated settlement process. This is meaningful behavioral context beyond the annotations.

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 with no redundancy. The description efficiently communicates the action, scope, and a key behavioral trait (escrow and manual payment) in a compact structure.

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?

With 3 parameters, no output schema, and a non-trivial mutation operation, the description is too sparse. It doesn't clarify the return value, the need for btcAddress despite it being optional in the schema, or the side effects of escrowing gas.

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?

With 0% schema coverage, the description must explain parameters but only hints at gasAmount via 'earned gas.' It fails to describe btcAddress and paymentDetails, leaving their purpose and requirement ambiguous. The Bitcoin context partially compensates, but not enough.

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 states a specific verb 'Request' and a clear resource 'Bitcoin cashout of earned gas,' making the core purpose unambiguous. It partially distinguishes from the sibling 'cash_out' by scoping to earned gas, though it doesn't explicitly name that sibling as an alternative.

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?

There is no explicit guidance on when to use this tool versus alternatives like 'cash_out.' The context implies you should use it when you have earned gas, but it doesn't state when not to use it, prerequisites, or compare with other tools.

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