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

The description adds important behavior beyond the annotations: it is a public ticker endpoint, returns only the last price, and costs $0.002 USDC per successful call via x402, with failed calls not charged. These payment and failure-charging details are operationally critical and not present in 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?

The description is front-loaded with the core purpose and follows with useful scope and pricing details. Every sentence adds distinct value, and there is no 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?

For a simple one-parameter price lookup with an output schema and read-only annotations, the description provides everything an agent needs: what it returns, what it does not return, and the payment model. No important invocation context is missing.

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%, so the single required `symbol` parameter is already fully documented by the schema. The description reinforces that it is one trading pair and gives BTCUSDT as an example, but adds no semantics beyond the schema's own example.

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 and resource: 'Binance spot last price for one trading pair.' It also scopes the result tightly by saying only the last price is returned and no order book or history, which distinguishes it from the sibling orderbook-depth 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?

It clearly signals when the tool is appropriate by limiting scope to a single trading pair's last price and explicitly excluding order book and history use cases. However, it does not name alternative tools such as the Binance orderbook-depth sibling or other exchange ticker tools, so routing guidance is clear but not complete.

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