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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered, and the description usefully lists returned fields in the absence of an output schema. It does not explain pagination behavior beyond what the schema says, nor whether article_id/article_number narrow the result set or fetch a single record.

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 tight sentence that front-loads the resource and the field list; nothing is padded. The bare 'article.get.' token is unexplained noise but costs little.

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?

Listing return fields partially compensates for the missing output schema, which is good. But with no guidance on what article_id/article_number do and no statement of default listing scope, an agent cannot confidently decide whether to pass filters or paginate through everything.

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 coverage is only 50%: limit and offset are documented in the schema, but article_id and article_number have no description anywhere. The description says nothing about parameters, so it fails to compensate for the undocumented filter arguments.

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 ('List') and resource ('products and services') and even enumerates the returned fields (article number, type, title, unit price, VAT, unit), which clearly separates it from fastbill_create_article. It does not explicitly contrast with other list_* siblings, but the resource is unambiguous.

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?

There is no statement of when to use this tool versus alternatives (e.g. create_article, or any product-lookup path), and no prerequisites or exclusions. The trailing 'article.get.' hints at the backing endpoint but gives no usage condition.

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