Veroq

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

No annotations provided, but description discloses critical behavioral traits: cost ('1 credit'), return structure ('Array of briefs with headline, confidence score...'), and implicit read-only nature via 'Get'. Could improve by mentioning rate limits or pagination, but covers essential operational costs.

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). Front-loaded purpose statement with zero filler. Every sentence serves a distinct function (purpose, usage guidance, output contract, cost disclosure, input example).

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 listing tool despite missing output schema: explains return values in description, covers cost, provides usage context against 45+ siblings, and includes working example. No gaps given the 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% providing baseline 3. Description adds value via concrete JSON example showing realistic values ('Markets', 10) that clarify expected input formats beyond the schema's basic descriptions, particularly helpful for the 'category' parameter which lacks enum values.

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 'Get' + resource 'verified intelligence briefs' + ordering constraint 'reverse-chronological'. Explicitly distinguishes from sibling tool veroq_search by contrasting 'browsing without a specific search query' vs search functionality.

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 exact context ('browsing recent news without a specific search query') and names the specific alternative tool ('Use veroq_search when you have a topic in mind'), providing clear decision criteria.

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