fiken_list_sales

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context of its own — nothing about pagination defaults, result ordering, volume limits, or what a page of results contains — despite page/page_size parameters implying paginated delivery.

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 zero filler, and the core action is front-loaded ahead of the optional constraint. Its brevity is appropriate structurally, though it borders on under-specification given the five-parameter schema.

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?

With five parameters at 0% schema coverage and no output schema, the description should explain pagination behavior and the required company_slug. Instead it covers only the date filter, leaving an agent unable to call the tool correctly beyond the simplest case.

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%, so the description must carry the burden, but it only clarifies the date format (YYYY-MM-DD) for date_from/date_to. The three other parameters — page, page_size (default 100), and the required company_slug — receive no explanation of meaning, format, or constraints.

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?

States a specific verb and resource ("List salg") plus an optional date scoping, so an agent knows it retrieves sales records. It does not differentiate from near-siblings such as fiken_list_invoices or fiken_list_transactions, leaving ambiguity about whether sales and invoices overlap.

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?

"eventuelt avgrenset på dato" only signals that the date filter is optional; it gives no indication of when to choose this tool over fiken_list_invoices or fiken_list_transactions. No prerequisites, exclusions, or alternative routing are provided.

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