netintel_currency_exchange

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: not whether the rate is mid-market or bid/ask, not the base/quote convention, not what happens on unsupported currency codes or future dates, and not any auth or rate-limit behavior. 'Real-time or historical' is the only real behavioral signal.

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 short sentences, front-loaded with the core capability and followed by the one actionable parameter hint. No filler or redundancy.

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?

A four-parameter tool with no annotations and no output schema needs the description to explain inputs, defaults, and return shape. The description omits amount handling, currency-code format, error behavior, and — critically — the boundary against the batch and history siblings, leaving the agent to guess which of the three to call.

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 0%, so the description must compensate, and it only partially does: it gives the date format (YYYY-MM-DD) but says nothing about 'amount' (optionality, default of 1?), or whether 'from'/'to' expect ISO 4217 codes, symbols, or names. Two of four parameters are effectively undocumented.

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?

States a specific verb (convert) and resource (currencies) with a scope detail (32 currencies, real-time or historical). It does not, however, distinguish itself from the sibling tools netintel_currency_exchange_batch and netintel_currency_exchange_history, and the historical-lookup sentence actively blurs the line with the latter.

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 only usage cue is 'pass a date for historical lookup,' which is a parameter instruction rather than guidance on when to choose this tool over currency_exchange_history or currency_exchange_batch. No exclusions, no prerequisites, no statement of when the real-time path is appropriate.

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