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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds value beyond them by disclosing the required admin.group permission and the concrete failure mode with an agent-only token, which the annotations do not convey.

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 dense sentences with zero waste: payload contents first, then permission prerequisite and failure mode. Front-loaded and immediately actionable.

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 output schema, the description compensates by naming the returned fields, and it discloses the auth requirement that determines whether the call succeeds. Pagination behavior is left to the schema, which covers it adequately; only the absence of any routing guidance keeps this from being fully complete.

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% and both pagination parameters are documented inline, including the 'pass the previous reply's next_page' convention. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 resource — the ticket groups (queues) of the instance — and even enumerates the returned fields (ids, names, agent ids), so an agent knows exactly what it gets. It is naturally distinct from siblings like zammad_list_organizations or zammad_list_ticket_states, though it never names an alternative to reinforce that distinction.

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 implied by the resource and the disclosed prerequisite (admin.group permission; agent-only tokens fail with an authorization error), which is genuinely useful pre-call guidance. However, there is no explicit when-to-use vs. alternative statement — nothing says, for example, when to reach for groups instead of states or priorities.

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