Veroq

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

No annotations provided, so description carries full burden. Discloses return structure ('Array of briefs with headline, confidence, category, and summary'), cost ('1 credit'), and includes working example. Deducting one point for missing rate limits, caching behavior, or error handling details.

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 structure with clear section headers (WHEN TO USE, RETURNS, COST, EXAMPLE). Front-loaded with purpose statement. 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?

No output schema exists, but description fully compensates by detailing return format, fields, and total count. Covers cost implications. With only 2 well-documented parameters and clear sibling differentiation, description is complete for this tool's complexity level.

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 clear descriptions for both 'symbol' and 'limit'. Description provides a JSON example showing valid inputs, but does not add semantic meaning beyond what the schema already documents. Baseline 3 is appropriate given schema completeness.

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 opens with specific verb ('Get') + resource ('news headlines and briefs') + scope ('specific stock or crypto ticker'). Clearly distinguishes from siblings by contrasting with veroq_search (topic-based) and veroq_feed (general news).

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?

Explicit 'WHEN TO USE' section states exact use case ('For ticker-specific news') and names two specific alternatives with their distinct scopes ('veroq_search for topic-based search', 'veroq_feed for general news').

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