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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds provenance ('NLYRA's own node') and an equivalence claim ('same data as The Desk's chart'), but says nothing about rate limits, freshness, or auth.

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?

One tight sentence that front-loads the returned fields and ends with the source/provenance note. No filler; only slightly compressed given the parenthetical field list.

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 read-only candle fetch with 3 params, annotations cover safety and the schema covers parameters; the description even enumerates returned fields despite there being no output schema. It is missing only rate-limit/freshness context, which is non-critical.

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 coverage is 67%: the candles and timeframe parameters already carry descriptions with defaults, while the required 'token' param only has a regex pattern. The description adds no parameter meaning (no syntax, no default restatement), so the schema does the heavy lifting — baseline 3 is appropriate.

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 a specific verb+resource: candles (OHLC, USD volume, trades) for a Robinhood Chain token, plus the data source ('NLYRA's own node'). An agent can tell it returns price candles rather than risk/quote data, though it never names a sibling to contrast against.

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?

No when-to-use or when-not-to-use guidance. With overlapping siblings such as market_overview and quote_trade, the description gives no signal about which to choose for current price vs historical candles vs market-wide data.

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