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

Annotations indicate a write operation with an open-world effect, but the description adds no behavioral context such as transaction fees, delays, or side effects. It does not contradict annotations, but it also contributes nothing beyond what annotations already reveal.

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 text is extremely short, but this is under-specification rather than effective conciseness. It omits essential information about the tool's purpose and parameters, leaving the agent without necessary guidance.

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?

This is a three-parameter mutation tool with no output schema and no parameter documentation. The alias reference provides no operational clarity, and the tool is far from complete for an agent to invoke 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%, yet the description does not explain any of the three parameters. gasAmount, btcAddress, and paymentDetails have only basic type and constraint information in the schema, and the tool description offers no clarification about their purpose or format.

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 only says it is an alias for request_cashout, without stating what cashing out actually does. The '[Sell]' prefix offers a vague hint, but there is no explicit verb or resource. It does not meaningfully distinguish this tool from its siblings beyond referencing another tool.

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?

No guidance is provided on when to use this tool versus request_cashout or other selling tools. There is no mention of context, prerequisites, or situations where this alias should be preferred.

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