veroq_ticker_price

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

No annotations provided, but the description lists return fields and notes the tool is free (0 credits). It does not mention side effects or rate limits, but for a simple read-only price check, 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?

Very concise: two sentences plus structured sections for WHEN, RETURNS, COST, EXAMPLE. No wasted words, front-loaded with key info.

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 all needed aspects: purpose, usage guidance, return fields, 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% with a good description for 'symbol'. The description adds an example and clarifies it works for stocks and crypto, providing context 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?

The description clearly states the action 'Get', the resource 'live market price', and specifies it works for both stock and crypto tickers. It distinguishes from sibling 'veroq_full' which provides full 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?

Explicitly states when to use ('quick price check'), notes it's free, and directs to 'veroq_full' for full analysis, providing clear alternatives.

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