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

The description adds vital behavioral and operational context beyond the structural hints, specifying the financial model ('0.0005 USDT per 100 rows') and the required operational steps ('Payment and signing steps'). This is essential for a 'premium' tool definition.

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 dense but organized logically: data type, cost, and execution steps. Every piece of information, including the alternative routes, appears to be necessary for the tool's operational viability.

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?

Despite detailing how and for how much the data is delivered, the definition is incomplete because it omits the semantics of the input schema. An agent cannot meaningfully select the correct parameters without this explanation.

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 fails to explain what the input parameters (to, from, limit, cursor, filters) represent or what they control. It focuses entirely on the execution and cost structure rather than the functional inputs.

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 resource provided: 'Premium token supply data.' It is precise about the type of data returned, which is helpful for an agent deciding on the tool's applicability.

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?

This is exceptionally clear, offering two distinct methods for consumption. It explicitly routes 'Wallet-holding agents' away from this paid method and toward a standard HTTP endpoint and a different cost structure.

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