get_klines

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

Excellent disclosure of behavioral specifics: exact allowed interval strings, limits range, default behavior, and response time format. Since no annotations are provided, the description carries the full burden, and it delivers concrete operational details beyond what the schema shows.

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?

Compact, efficient description with critical constraints front-loaded (interval mandatory, limits). Could be slightly more structured, but the key information is dense and immediately useful.

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 market data tool with no output schema, it covers the core requirements: intervals, limits, end time, and response time format. The absence of explicit return-structure details is acceptable given there's no output schema to reference.

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 schema has 0% description coverage, so the description must compensate. It does so by explaining interval enumeration, limit range and default, plus end_time_ms semantics (0 = now). This adds real meaning beyond the bare schema types.

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?

Clearly states 'Candlesticks for a symbol' with a specific verb (get) and resource (klines/candlesticks). It distinguishes itself from siblings like get_klines_history and get_price by specifying the exact interval format and response detail (epoch milliseconds).

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?

Implies usage by specifying mandatory interval and limit constraints, but does not explicitly state when to use this versus get_klines_history or other market data tools. The conditional context (recency, specific intervals) could be more explicit for agent routing.

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