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

With no annotations, the description carries the transparency burden. It discloses authentication requirements (bearer token or payment via Binance/x402), which is valuable context. However, it does not mention whether the operation is read-only, potential rate limits, or data freshness, and the payment details are verbose without adding functional clarity.

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 a single dense paragraph that front-loads payment/authentication details before explaining the actual purpose. The payment breakdown (Binance b402, USDT, USDC, USD1 or U, BNB Smart Chain, x402, USDC, Base network) is lengthy and better suited for a separate auth section. The core functionality is buried in the middle, making it less scannable.

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 tool has an output schema and one optional parameter, the description covers the essential functional purpose and the unusual payment/auth context. However, it omits behavioral details like rate limits, read-only status, and any edge cases. The verbose payment info does not fully compensate for these gaps.

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 single parameter 'chain' has an enum in the schema but no description (0% schema coverage). The description compensates by explaining 'per chain' and 'Omit chain for all nine', which clearly clarifies the optionality and default behavior. This adds meaningful semantic 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 clearly states the tool provides 'Support and resistance price walls per chain with touch counts, from hourly to weekly market structure.' This identifies the resource and scope, and distinguishes it from sibling tools by its unique output. However, it lacks a verb like 'get' or 'list', making it slightly less direct.

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 gives guidance on how to use the chain parameter ('Omit chain for all nine') and explains authentication/payment options, which is useful. However, it does not explicitly state when to use this tool over sibling alternatives or provide exclusions, leaving the when-to-use context only implied.

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