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

No annotations are present, so the description carries full burden for behavioral disclosure. It does not mention that this is a read-only operation (though implied), nor describe pagination, limit behavior, error cases, or data ordering. Lacks caution about rate limits or potential overhead.

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 extremely concise (one sentence), but it is under-specified rather than efficiently concise. The length is appropriate, but the content is minimal; there is no front-loading of the most important usage constraints.

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 data retrieval tool with no output schema and only one required parameter, the description might be minimal but still lacks essential context like default behavior (returns recent candles?), max limit, and how to interpret timeframes. An agent could misuse limit or be unaware of the need for a specific mint format.

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%, and the description does not explain any of the three parameters. The meaning of 'mint' is obvious to a crypto domain but not explicitly stated; 'limit' and 'tf' are only defined by defaults and enum. With zero coverage)Skip the description is a non-compensating failure.

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?

States the verb and resource ('OHLC candle data for a token') and lists the valid timeframes glassily. It doesn't name a sibling tool with similar purpose, but among the many siblings it is clearly distinguished by the resource type (candles).

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?

Gives no guidance on when to use this tool versus alternatives, when not to use it, or prerequisites. The context is minimal; an agent would not know if this is for recent price action or historical data, or if there are constraints like token must be a known mint.

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