Manage custom exchange rate

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 discloses that extended write profile is required, which is a behavioral trait. However, it does not reveal side effects (e.g., whether delete reverts to system rate, whether setting overrides existing rate) or any irreversible consequences. This is basic but incomplete for a mutation tool.

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 two sentences, front-loaded with the core action and followed by a necessary permission note. There is no fluff or redundant information.

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 has no output schema, so the description should explain effects or return values, but it doesn't. It also omits context on how custom rates interact with system rates or user-specific behavior. It is minimally adequate but lacks important 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?

Schema description coverage is 0%, so the description must compensate. It only mentions 'set or delete' (reflecting the operation parameter) but provides no explanation of what 'rate' should look like or what 'currency' refers to. The schema's maxLength/minLength for currency is present, but the description adds no semantic value beyond the parameter names.

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 function: 'Set or delete a user custom exchange rate.' It uses a specific verb ('set'/'delete') and resource ('custom exchange rate'), and this distinguishes it from sibling tools like get_exchange_rates, which is read-only.

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 for setting or deleting a custom rate, but it doesn't explicitly compare to alternatives or state when to use this vs. other rate-related tools. The mention of 'Requires extended write profile' provides a prerequisite, which is useful but not sufficient for clear when-to-use guidance.

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