bexio Currencies

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

Discloses beyond annotations: delete is permanent and cannot be undone; update is PATCH only changes round_factor. This aligns with destructiveHint=true and adds critical behavioral detail.

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?

Description is a single paragraph but efficiently covers all actions and parameters. Slightly dense; could benefit from bullet points for readability, but no unnecessary content.

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?

Covers all 7 parameters, schema descriptions present, annotations provide destructive hint. No output schema needed; description adequately explains each action's behavior and required inputs.

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 coverage is 100%, so baseline 3. Description adds value by explaining embed example ('exchange_rate'), date format ISO 8601, limit max 2000, and payload examples ('CHF', 0.05).

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 manages currencies and reads exchange rates, listing specific actions (list, get, create, update, delete, list_codes, list_exchange_rates) that distinguish it from other bexio sibling tools.

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?

Each action has context (e.g., list with optional parameters, update only round_factor, delete permanent). However, no explicit when-not-to-use or comparison to alternatives, though none exist for this resource.

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