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

No annotations are supplied, so the description must carry behavioral weight; it does disclose the hard cap of 200 candles and the default of 80, which prevents accidental over-fetching. It says nothing about response shape, behavior on an unknown mint/symbol, or rate limits, which matters for a data-fetch tool with zero annotation coverage.

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 dense sentences, front-loaded with the resource and scope, then the parameter facts, then the routing rule. No filler or restatement of the title.

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 three-parameter read-only data tool with no output schema, the description covers scope, all parameter values, the cap, and the sibling alternative. What is missing is minor: confirmation of whether OHLC values are denominated in USD/ETH and what happens when the token is unknown.

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 documents all three parameters: the tf enum values, the limit maximum and default, and the token identifier. The only ambiguity is 'mint or symbol', which implies the mint field accepts a symbol while the schema names the field 'mint' and gives no format hint.

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?

Names a specific resource and output shape (OHLC price candles) scoped to exactly one X1 token, and immediately distinguishes itself from the price-lookup sibling. An agent can tell what this returns and for what granularity without opening the schema.

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?

Explicitly states the exclusion case: 'For the current price alone use token_lookup', which is a real routing rule. It stops short of guiding timeframe selection or naming other market-data siblings (e.g. arc_price, recent_trades), so it is clear context without full alternative coverage.

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