Veroq

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

No annotations provided, but description discloses COST (2 credits) and detailed RETURNS structure (signal counts + full indicator values). Could explicitly state read-only nature, though 'Get' verb implies this.

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?

Excellent structured format with labeled sections (WHEN TO USE, RETURNS, COST, EXAMPLE). No filler text; every line provides actionable information for tool selection and invocation.

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, description compensates with detailed RETURNS section explaining signal summaries and indicator values. Includes cost information critical for API resource management. Complete for a 2-parameter read operation.

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 100% with complete parameter descriptions. Description adds value through EXAMPLE block showing JSON usage pattern {'symbol': 'TSLA', 'range': '6mo'}, which illustrates practical invocation beyond schema definitions.

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?

Description explicitly states 'Get all major technical indicators' with specific examples (RSI, MACD, Bollinger Bands, moving averages) and distinguishes from sibling tool veroq_candles by stating 'Use veroq_candles for raw price data instead.'

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?

Contains explicit 'WHEN TO USE' section specifying 'For pre-computed technical analysis' and explicitly names alternative tool (veroq_candles) for raw price data, providing clear selection criteria.

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