add_currency_conversion_calc_group

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

With no annotations provided, the description carries the burden of disclosing behavior. It explicitly describes that the tool creates two calculation items and the exchange-rate formula, which is meaningful behavioral context. However, it does not mention potential side effects, prerequisites, or idempotency, so it is not fully transparent.

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 a single sentence, front-loaded with the verb 'Create', and contains no wasted words. Every element contributes to understanding the tool's function.

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?

The tool is moderately complex with 6 parameters and no output schema. The description captures the core behavior but omits details such as how the currencyColumn is used, prerequisites (e.g., base table must be single-column, but that is in schema), and possible interactions with existing calc groups. It is adequate but not comprehensive.

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 description coverage is high (83%), so the baseline is 3. The description adds some semantic context for rateTable and rateColumn by explaining the SUMX formula, but it does not elaborate on sessionId, precedence, or the currencyColumn beyond schema descriptions. It provides marginal added value.

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 the tool's purpose: creating a currency-conversion calculation group, specifying its structure (Original Value item and Converted item) and the formula (SUMX over Date * rate). This is specific and distinguishes it from generic sibling tools like add_calculation_group and add_time_intelligence_calc_group.

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 description implies when to use the tool, i.e., when creating a currency-conversion calculation group. It does not explicitly mention alternatives or exclusions, but the specialized nature is evident from the name and description. A clear context is provided without explicit when-not guidance.

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