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

Annotations already cover the read-only/idempotent/non-destructive profile, so the description's job is to add context — and it does: it discloses that no-slug returns an index of articles and that content is German. It doesn't describe article length or structure, but that is minor given the safety hints.

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, the mode-switching behavior front-loaded after the topic list. The parenthetical topic enumeration is somewhat long but serves as useful scope-setting rather than filler.

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?

There is no output schema, so the description correctly compensates by telling the agent what it gets back in each mode (article vs. list) and in which language. Sufficient for a single-optional-param read tool.

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 100% with an enum of the ten valid slugs, so the schema carries most weight. The description adds value by explaining the semantics of omission ('Ohne slug: Liste der Artikel'), which the schema's 'Artikel (optional)' does not spell out.

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 concrete resource (seller guides) with an enumerated topic list, and clarifies that omitting the slug yields an article list. It is clearly distinguishable from the sibling fee/calculator tools, though the verb 'read' is only implied by the name rather than restated.

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?

'Ohne slug: Liste der Artikel' gives an explicit condition for the two modes of use (list vs. fetch one article). It does not, however, mention when an agent should prefer calculate_amazon_fba_profit or estimate_fba_fee over consulting a guide.

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