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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior: results are paged and the next page token is fed back in as 'page'. It says nothing about rate limits, auth requirements, default ordering, or total counts, which is acceptable for a simple read-only list but not rich.

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?

Three tight sentences, front-loaded with the resource identity, then filters, then pagination. No filler; the trailing endpoint reference (GET /v1/articles) costs little and no sentence overstays its usefulness.

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 no output schema, the description correctly compensates by naming the core returned fields (price, tax rate, unit) and by explaining the paging contract. It is close to complete for this tool; only the absence of ordering/sorting behavior and total-count semantics keeps it from a 5.

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 the baseline is 3. The description goes slightly beyond the schema by grouping the filters conceptually as 'exact' matches and by revealing that 'next_page' originates from the previous reply (a response-side detail absent from the input schema and from any output schema).

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 articles') and immediately clarifies the domain meaning ('products and services usable as invoice line items') with the returned fields (price, tax rate, unit). This distinguishes it from the singular sibling lexware_get_article and from the other list_* tools without the agent needing to open a schema.

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?

It states the conditions for the optional filters ('exact filters by article number, GTIN or type') and explains pagination mechanics ('Paged: pass next_page as page'), giving clear operational context. It stops short of explicit when/when-not guidance — e.g. it never says to use lexware_get_article when a single article is known — so there is no exclusion language.

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