explain_guard_productExplain the Guard product using CurrencyGuard's approved product and FAQ content. Covers: what the Guard is, how it works, who it is for, how it compares to forwards or options, and legal, regulatory, accounting, or eligibility questions.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read operation. Description adds that the tool uses approved product and FAQ content, implying no side effects or dynamic 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?
Two efficient sentences, front-loaded with purpose, then list of covered topics. No redundant words.
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?
With no parameters and no output schema, the description fully covers the tool's behavior (explanation using approved content) and scope. No gaps.
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?
Input schema has zero parameters, so description cannot add parameter meaning. Baseline 4 applies as no extra semantics needed.
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 explains the Guard product and enumerates specific topics (how it works, comparisons, legal questions). It distinguishes from sibling tools that deal with rates or pricing.
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 usage when an explanation of the Guard product is needed. Sibling tools are clearly different (rates, settlement), but no explicit when-not-to-use or alternative guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: explanation, rate queries (spot, forward, historic), supported currencies, pricing, extension pricing, and date resolution. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (e.g., explain_guard_product, get_forward_rate). Verbs are descriptive and uniform.
8 tools cover the core functionality of pricing and explaining a currency hedging product without being excessive or insufficient. Each tool serves a clear purpose.
The tool set covers explanation, rate information (spot, forward, historic), supported currencies, initial pricing, extension pricing, and date resolution – a complete workflow for quoting and understanding the Guard product.