Veroq

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

With no annotations provided, description carries full disclosure burden. It documents cost ('2 credits'), return behavior differences between summary/detail modes, and argument-dependent execution paths (no args vs. slug). Lacks explicit read-only safety declaration, but 'Get' and return descriptions imply non-destructive behavior.

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 formatting with clear section headers (WHEN TO USE, RETURNS, COST, EXAMPLE). Information is front-loaded with the core function, followed by contextual sections. Zero wasted words; every sentence provides actionable guidance or constraints.

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 tool with no output schema, description comprehensively covers return values (summary vs. detail modes), cost constraints, sibling differentiation, and usage examples. Addresses all gaps left by missing structured metadata, providing complete context for correct invocation.

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?

Despite 100% schema coverage (baseline 3), description adds value by explaining behavioral semantics: omitting arguments triggers summary mode while passing a slug triggers detailed history. Includes concrete JSON example showing parameter usage patterns not evident from schema alone.

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' and resource 'macroeconomic indicators from FRED', clearly defining the tool's function. It distinguishes from sibling 'veroq_economy_indicator' by explicitly stating when to use the alternative, clarifying the tool's scope within the suite.

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 listing specific data types (GDP, CPI, unemployment, fed funds rate). Explicitly directs users to sibling tool 'veroq_economy_indicator' for single indicator history, providing clear alternative routing and preventing tool selection errors.

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