set_default_currency

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

Discloses that it creates a company currency if needed and fails if invoices exist for that currency. However, no annotations provided, so description carries burden. Lacks info on authorization, idempotency, or safety.

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?

Concise three sentences, front-loaded with purpose ('Set the company default currency'), no wasted 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?

For a mutation tool with 1 parameter, covers main behavior and failure condition but does not explain return value or side effects. Adequate but could be more complete.

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% and description repeats 'Required: currencyId (global currency ID)' adding no new semantic meaning beyond the schema. Baseline of 3.

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?

Clearly states the action: set company default currency. Specifies endpoint and required parameter. Distinguishes from siblings like 'create_currency' (create a new currency) and 'get_default_currency' (retrieve).

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?

Provides a failure condition (fails if invoices with that currency) but does not explicitly guide when to use this tool vs alternatives like 'create_currency' or 'get_default_currency'. No exclusions or alternatives mentioned.

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