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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds non-obvious behavioral context the annotations cannot convey: results are permission-scoped (agents see only their groups' tickets, customers only their own) and it exposes the expand=true query behavior. It does not describe pagination mechanics or result shape, but the schema covers paging and this is a read-only list.

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, zero filler, with the visibility constraint front-loaded and the routing hint placed after the primary behavior. The endpoint reference is a compact extra.

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 read-only, no-output-schema list tool with fully documented inputs, the description covers purpose, scope/authorization, and the sibling alternative. Return format and pagination behavior are left implicit, which is acceptable given the schema documents next_page/per_page paging.

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 only two optional paging parameters, so the schema already carries the parameter documentation; baseline 3 applies. The description's mention of 'expand=true' adds a hint about response expansion not present in the schema, but it is not tied to a described input parameter.

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 (tickets) and immediately defines the scope: only tickets the token's user can see, with the agent/customer visibility rule spelled out. It also names the sibling zammad_search_tickets as the alternative, so the agent can distinguish the two without opening either schema.

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?

Explicitly gives the when-to-use split: use this for unfiltered listing, use zammad_search_tickets 'for anything targeted.' That is a clear alternative-routing rule rather than an implied one.

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