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 value by naming the shape of the returned records (code, name, sale/purchase price, tax, unit, stock levels), which matters since there is no output schema, but it says nothing about result caps, paging behavior, currency/price formatting, or which fields may be null.

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 tight sentences, front-loaded with the verb and resource before the field list. The final clause about article_id is compact and useful as a cross-reference, though it reads as a fragment and could be stated more clearly.

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 does the necessary work of naming the returned fields, and the fully documented schema handles all six parameters. For a simple read-only list tool this is close to sufficient; only paging/limits context and explicit sibling disambiguation are absent.

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%, with each of the six parameters documented in the schema (including next_offset guidance and the order_by enum), so the baseline is 3. The description only alludes to code/name as search keys and adds no syntax, casing, or partial-match nuance beyond what the schema already says.

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 or search items / products (Artikel)") and enumerates the fields the resource carries, plus the German domain term so an agent can match user vocabulary. The resource name alone distinguishes it from the other bexio_list_* siblings (invoices, contacts, taxes, etc.), though it never explicitly says which sibling to prefer.

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?

"List or search" plus the code/name filter semantics implies you pass filters to narrow results, and the trailing sentence says what to do with a returned id (use as article_id in a draft invoice). There is no explicit when-to-use vs. when-not, and no prerequisite or exclusion guidance.

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