veroq_technicals

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

With no annotations, the description carries full burden. It discloses cost (2 credits), return structure (signal summary and indicator values), and provides an example. However, it does not explicitly state that the tool is read-only or requires authentication, but the context implies no mutations.

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 concise and well-structured with clear sections for when to use, returns, cost, and example. Every sentence adds value, and there is no redundant or missing information.

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?

Despite no output schema, the description details the return values (signal summary, indicator values). It covers inputs, outputs, usage context, and cost, making it complete for an agent to select and invoke correctly.

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 100%, so baseline is 3. The description adds an example and lists 'symbol' and 'range' but does not provide additional semantic meaning beyond the schema's own parameter descriptions.

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 retrieves major technical indicators (RSI, MACD, Bollinger Bands, moving averages) and an overall signal summary. It distinguishes itself from sibling 'veroq_candles' by specifying it returns pre-computed analysis rather than raw price data.

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?

Explicit 'WHEN TO USE' section guides the agent to use this tool for pre-computed technical analysis and directs to 'veroq_candles' for raw data. This provides clear context and alternatives, helping avoid incorrect tool selection.

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