romaco_get_visible_candles

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

No annotations provided, so description carries full burden. It discloses token cost, compression behavior, and the difference between summary and raw array. Lacks details on rate limits or idempotency, but sufficient for a read-only operation.

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?

Concise, front-loaded first sentence states core purpose. Subsequent sentences cover cost and usage caveats without redundancy. Every sentence adds value.

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 one-parameter tool with no output schema, the description covers functionality, cost, and when to choose raw vs. summary. References sibling tool for analysis, making it complete.

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?

Single boolean parameter has schema description with cost warning. The description adds context on when to use raw mode and approximate size (70 KB), reinforcing and clarifying the schema.

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 it summarizes OHLCV candles visible in the chart viewport, listing specific statistics (count, first/last, OHLC range, etc.). It distinguishes from siblings by explicitly recommending romaco_analyze_market for analysis.

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?

Provides explicit guidance on when to use the compressed summary vs. raw array ('only opt in when user explicitly asked for raw candles'). Also suggests alternative tool for analysis, making usage boundaries clear.

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