fiken_list_purchases

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld behavior, so the safety profile is covered. The description adds only the date-format hint and nothing about pagination defaults (page=0, page_size=100) or the existence of supplier filtering, so it contributes little beyond structured fields.

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?

A single short sentence with the resource front-loaded and the optional filter second – no wasted words. It is efficient, though its brevity borders on under-specification rather than pure 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?

For a 6-parameter tool with no output schema and zero schema description coverage, the description should at minimum explain pagination and the supplier filter. It covers only the date range, leaving key parameters and result behavior undocumented.

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% across 6 parameters, so the description carries the full burden. It documents the date format (YYYY-MM-DD) for date_from/date_to, but says nothing about page, page_size, or the supplier_id filter, which is a significant omission.

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 gives a specific verb ('List') and resource ('kjøp/leverandørbilag' – purchases/supplier vouchers), which lets an agent distinguish it from the singular fiken_get_purchase. It does not explicitly differentiate itself from adjacent list tools like fiken_list_purchase_drafts or fiken_purchase_history, but the resource is clear enough.

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 phrase 'eventuelt avgrenset på dato' implies the date filter is optional, which gives minimal usage context. There is no guidance on when to choose this tool over fiken_list_purchase_drafts, fiken_purchase_history, or fiken_find_duplicate_purchases, and no mention of filtering by supplier.

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