veroq_fast_movers

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

The description discloses return format (array of tickers with scores and delta) and cost (1 credit). With no annotations, it carries the transparency burden well, but could further clarify data recency or cycle length.

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?

Extremely concise with structured sections (WHEN TO USE, RETURNS, COST, EXAMPLE). Every sentence is informative, and the example placeholder is harmless. No wasted words.

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?

Given no parameters and no output schema, the description fully covers purpose, usage, return format, and cost. It is complete for a query tool with no inputs.

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?

The input schema has zero parameters, so the description correctly adds no parameter details. Baseline for zero parameters is 4, and the description meets that without redundancy.

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 the tool identifies tickers with the biggest signal changes. It uses a specific verb ('identify') and resource ('tickers with biggest signal changes'). However, it does not explicitly differentiate from siblings like veroq_fast_signals or veroq_market_movers, leaving room for confusion.

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?

A dedicated 'WHEN TO USE' section explains its suitability for momentum or reversal detection. It provides clear context but lacks explicit when-not-to-use instructions or alternatives.

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