veroq_ticker_score

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

No annotations, but description discloses cost (2 credits) and return structure (composite score, signal, component breakdown). It does not mention side effects, but as a read operation, this is sufficient.

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?

Description is extremely concise with clear sections (WHEN TO USE, RETURNS, COST, EXAMPLE). Every sentence adds value, no redundancy.

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 tool with one parameter and no output schema, the description fully covers purpose, usage context, return values, cost, and an example. No gaps.

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% for the single parameter 'symbol', which is well described. The description adds an example request `{ "symbol": "NVDA" }`, providing extra clarity beyond 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?

Description clearly states it gets a composite trading signal score for a ticker based on sentiment, momentum, coverage volume, and event proximity. It distinguishes from sibling tool veroq_ticker_analysis, which provides deeper context.

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?

Explicitly provides 'WHEN TO USE' guidance: for a quick bull/bear signal on a ticker, and directs to use veroq_ticker_analysis for deeper context. Clear when-to-use vs alternative.

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