ksef_token_list

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

Annotations provide readOnlyHint=true, and the description adds meaningful behavioral context beyond that: it requires an active session and explicitly states that it returns only metadata and never token values. This is valuable safety-relevant transparency for an AI agent.

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 short, information-dense sentences. The main purpose is front-loaded, followed by the key prerequisite and a crucial behavioral warning. No filler or redundancy.

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 simple read-only list operation with two optional, fully documented parameters, the description is adequately complete. It covers the active-session requirement and the metadata-only output. It does not describe the return structure, but no output schema exists and pagination is inferrable from the continuationToken parameter.

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?

The input schema already documents both parameters completely (pageSize with range/default, continuationToken as the pagination continuation token). The description adds no additional parameter-level meaning, so the schema carries the burden and the baseline of 3 is appropriate.

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 a specific verb and resource: 'Wyświetl listę tokenów KSeF' (display the list of KSeF tokens). This distinguishes it from sibling tools like ksef_token_generate, ksef_token_get, and ksef_token_revoke, which perform different operations.

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 description provides a clear prerequisite — 'Wymaga aktywnej sesji' (requires an active session) — which helps an agent understand when the call can succeed. However, it does not explicitly state when to use this tool versus alternatives like ksef_token_get, nor does it mention when not to use it.

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