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

readOnlyHint=true already tells the agent this is a safe read, so the description's main additions are the underlying endpoint (GET /katalog) and the returned field set. It says nothing about result volume, ordering, pagination, or whether the whole catalog comes back in one call — meaningful gaps for a list operation against a catalog.

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 sentences: the first front-loads the action and the payload contents, the second pins the backing endpoint. Every clause carries information and nothing is padded.

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 parameters and no output schema, the description usefully compensates by enumerating the returned fields, which is exactly what an agent needs to plan post-call handling. The remaining gap is operational: no guidance on result size or paging for a catalog list.

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 tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly signals a no-argument call rather than implying hidden filters.

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') plus resource ('products and services in the Solo catalog') and even enumerates the fields returned (code/sifra, KPD code, description, unit, quantity, price, discount, tax rate). The resource is inherently disjoint from the sibling tools (invoices, offers), so no agent could confuse it with them.

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?

Usage is only implied: an agent can infer this is the tool to reach for when it needs catalog items rather than invoices or offers, but the description never says so explicitly. There are no stated preconditions, no exclusions, and no mention of how to narrow or page a potentially large catalog.

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