Veroq

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

No annotations provided, so description carries full burden. It discloses 'COST: 2 credits' and details the return structure ('Array of events with type, subject, headline...') which compensates for lack of output schema. Does not mention pagination, rate limits, or error conditions.

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. Every line provides unique information; no repetition of schema details or tautology.

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 2-parameter query tool with no annotations and no structured output schema, the description is complete. It compensates for missing output schema by detailing return fields, provides cost information critical for credit-aware agents, and includes a valid usage example.

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 basic descriptions ('Event type to filter by'), so baseline is 3. The EXAMPLE section adds significant value by showing concrete parameter values ('earnings', 'NVDA'), helping the agent understand expected formats and that both filters can be used together.

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 notable events detected across intelligence briefs') and clarifies scope with examples ('significant developments, announcements, and inflection points'). The 'WHEN TO USE' section further distinguishes it from siblings by focusing on 'major events' like product launches and policy changes.

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 the tool is for discovering 'major events like product launches, policy changes, or market-moving announcements' and notes filtering capabilities. Lacks explicit named alternatives from the 40+ sibling tools, but provides clear contextual guidance.

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