fiken_create_purchase

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

Annotations indicate readOnlyHint=false, which is consistent with 'creates'. The description adds that amounts are in NOK øre, providing useful unit context. However, it does not disclose other behaviors (e.g., whether a purchase or draft is created, required permissions, side effects).

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 concise sentences, front-loaded with the action. No extraneous words, but could be slightly more informative without losing conciseness.

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?

This is a complex mutation tool with 13 parameters, 5 required, and no output schema. The description provides minimal context: only purpose and unit. Missing details about return value, necessary prerequisites (e.g., company ID), and side effects.

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 54%, so the schema already describes many parameters. The description adds 'Amounts in NOK øre' which applies to all amount fields, supplementing the schema. It does not explain specific parameters further, but the coverage is moderate.

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 it creates a new purchase, which is a specific verb and resource. It minimally distinguishes from siblings like fiken_create_purchase_draft or fiken_list_purchases, but the name itself provides clarity.

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 given on when to use this tool versus alternatives (e.g., fiken_create_purchase_draft for drafts, or typical use cases for cash vs supplier). The description lacks context on prerequisites or scenarios.

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