Veroq

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

No annotations provided, so description carries full burden. Discloses critical cost behavior ('COST: 2 credits') and implementation detail ('9 sources in parallel'). Documents return structure since no output schema exists. Does not disclose error handling or cache behavior, preventing a perfect score.

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?

Perfectly structured with clear section headers (WHEN TO USE, RETURNS, COST, EXAMPLE). First sentence establishes purpose; subsequent sentences earn their place with specific operational metadata. No filler text despite covering multiple dimensions.

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?

Comprehensive for a single-parameter tool without output schema. Compensates for missing output schema by detailing return categories. Covers cost (critical for credit-based APIs), differentiates from 40+ siblings, and provides usage example. Nothing essential is missing.

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 has 100% coverage (ticker symbol described), establishing baseline 3. The description adds value by providing a concrete JSON example ('EXAMPLE: { "ticker": "NVDA" }') that demonstrates exact invocation format beyond what the raw schema conveys.

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?

Opens with specific verb+resource ('Get the full profile for a ticker') and enumerates exact data categories returned (price, fundamentals, technicals, sentiment, news). Explicitly distinguishes from sibling veroq_ticker_analysis by contrasting 'complete data dump' vs 'interpreted 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?

Contains explicit 'WHEN TO USE' section stating 'For a complete data dump on a single ticker.' Directly names alternative tool with 'Use veroq_ticker_analysis for an interpreted analysis instead,' providing clear decision criteria between the two options.

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