veroq_fast_macro

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

No annotations are provided, so the description carries the full burden. It mentions 'pre-computed' and a credit cost, but lacks details on authentication, rate limits, failure modes, or update frequency. While it states 'RETURNS: Structured macro data', it does not elaborate on the structure or behavior beyond that.

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?

The description is concise and well-structured with clear headings (WHEN TO USE, RETURNS, COST, EXAMPLE). Each sentence adds value, and the content is front-loaded. No wasted text.

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?

Given the tool has no parameters and no output schema, the description adequately covers what data is returned (yields, CFTC, jobs, energy). However, it could be more complete by specifying data sources, update frequency, or format examples beyond the empty 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?

The input schema has no parameters, so schema coverage is 100% trivially. The description adds no parameter information, which is acceptable. Baseline score of 4 applies.

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?

The description clearly states it provides a macro snapshot combining treasury yields, CFTC positioning, jobs, and energy prices, using specific verbs like 'combining' and 'snapshot'. However, it does not explicitly distinguish itself from sibling tools like 'veroq_economy' or 'veroq_energy_overview', which may have overlapping 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?

The 'WHEN TO USE' section explicitly describes the use case: a single-call macro snapshot. It provides clear guidance on when to invoke this tool. It does not mention when not to use it or alternatives, but the context is sufficient for a simple zero-parameter tool.

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