list_categories

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

No annotations are provided, so the description carries the full burden; it explicitly states 'Read-only' and discloses that the call returns the entire menu hierarchy rather than a filtered subset. It does not cover auth/permission requirements or pagination, which are the remaining gaps for an unannotated tool.

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?

The description is short and front-loaded, leading with what the tool browses before drilling into return shape and parameter meaning. Every sentence earns its place, though the multi-line formatting is slightly loose for the amount of content.

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 an output schema present the description need not detail return values, yet it still sketches the group/categories structure. Combined with the parameter explanation and read-only note, an agent has enough to invoke it correctly; only auth/permission context is 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 0%, so the description must compensate, and it does: it defines what layout_slug selects, names the default ('grocery'), and gives two concrete hub values. It adds real semantic value beyond the bare string-typed schema property.

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+resource ('Browse the Lavka catalog menu: category groups with their categories') and enumerates the returned shape (group id/title, categories id/title). It also names the follow-up sibling get_category_products, so an agent can distinguish this listing tool from the sibling that consumes its output.

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?

Explains that a returned category id is used with get_category_products, which gives clear follow-on context, and clarifies that layout_slug selects the storefront with concrete alternatives ('grocery' default vs 'pharmacy'/'pet_store' hubs). It stops short of explicit when-not-to-use guidance, but the routing intent is clear.

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