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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that, but the bar is lower with annotations present and the description does not contradict them. No added context such as result volume or whether unfiltered listing returns the entire 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?

It is a single short line with no wasted words, but the brevity comes at the cost of under-specification rather than efficiency. The parenthetical translation is the only content beyond the name restatement.

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?

For a simple read-only two-parameter lister with full schema coverage and rich annotations, the minimum needed to call it correctly is present. Missing are practical details such as default result scope when both filters are omitted, which matter for a catalog listing 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 description coverage is 100%: 'search' (name, SKU, description) and 'category' are fully documented in the schema. The description adds no syntax, matching behavior, or combination hints, so the baseline 3 applies since the schema does the heavy lifting.

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?

The description gives a specific verb ('List') and resource ('catalog / price list items'), so the purpose is inferable without opening the schema. However, beyond restating the tool name and adding a Czech translation in parentheses, it offers no scope detail (all items vs. filtered, ordering, pagination) and does not reference the create_catalog_item sibling.

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 explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as create_catalog_item. Usage is only implied by the name 'list_' prefix following the list_* family convention.

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