bokio_list_uploads

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are paged, which is genuine behavioral context, but says nothing about page limits, total counts, or ordering; details like the 100-item page cap live only in the schema.

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 sentences, zero filler, with the core operation front-loaded and the redirect to the sibling immediately after. Nothing could be removed without losing information.

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 a full output schema, complete parameter descriptions, and read-only annotations, the description only needs to establish the listing scope and the download handoff, both of which it does. Minor gap: no guidance on how to paginate through a full result set.

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 100%, so every parameter (page, pageSize, query, companyId) is already documented with formats and constraints. The description adds no additional meaning about filtering or company scoping beyond what the schema states, so the baseline 3 applies.

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+resource: 'List uploaded files and receipts (kvitton) with paging.' The parenthetical synonym and the paging note make the scope unambiguous. It differentiates from bokio_download_upload but does not distinguish itself from the related bokio_get_upload sibling.

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?

'Use bokio_download_upload for a file's content' names the alternative and the condition that selects it, which is exactly the routing an agent needs. However, there is no explicit statement of when to reach for listing (e.g. discovering an upload id before downloading), and no exclusion for bokio_get_upload.

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