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: 2 credits' and details return structure ('Rate, change, change percent') since no output schema exists. Missing rate limits or auth requirements, but covers cost and return behavior well.

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 structured format with labeled sections (WHEN TO USE, RETURNS, COST, EXAMPLE). Every sentence serves distinct purpose; no redundancy. Front-loaded core purpose in first sentence.

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 single-parameter tool without output schema or annotations, description is comprehensive. Compensates for missing output schema by detailing return fields and timestamp behavior. Cost transparency completes the operational context.

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%, establishing baseline 3. Description elevates this by adding concrete example '{ "pair": "EURUSD" }' and clarifying the omit-for-all-pairs usage pattern beyond the schema's basic description.

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 combination ('Get current foreign exchange rates') that precisely defines scope. Clearly distinguishes from siblings like veroq_crypto and veroq_commodities by focusing exclusively on FX market data.

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 clarifies domain (currency exchange rates and FX market data). Explains the two invocation patterns (no args for all pairs, specific code for single pair), though it doesn't explicitly contrast with similar data tools like veroq_crypto.

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