fiken_create_sale

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

The description mentions amounts are in NOK øre, which adds useful behavioral context beyond the annotation (readOnlyHint=false). However, it does not disclose other traits like required permissions, side effects on accounting, or whether the sale is finalized immediately.

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 extremely concise with two sentences, front-loading the purpose immediately. Every word is useful, with no unnecessary elaboration.

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?

Given the tool's complexity (15 parameters, 5 required, no output schema), the description is insufficient. It does not explain required parameters, the structure of lines, or what constitutes a successful creation (no return value hinted).

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?

With schema description coverage at only 40%, the description fails to compensate. It does not explain key parameters like kind, lines, or customerId beyond what is in the schema. The brief mention of 'Amounts in NOK øre' only marginally helps for currency-related fields.

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 creates a new sale and mentions amounts in NOK øre, distinguishing it from related tools like fiken_create_sale_draft and fiken_create_invoice. However, it does not elaborate on the different kinds of sales (cash_sale, invoice, external_invoice) which are required parameters.

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?

No guidance is provided on when to use this tool versus alternatives such as fiken_create_invoice or fiken_create_sale_draft. The description lacks any context about prerequisites or exclusions.

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