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. The description adds real behavioral context beyond that: results are limited to the last 20 tickets and the scope is the caller's own tickets. It does not mention ordering beyond recency or pagination, which are minor gaps given the annotation coverage.

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, no filler. The operating mode is stated first and the high-risk disambiguation (internal ID vs. #12345) is placed last where it is most likely to be read before invocation.

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 single optional parameter and no output schema, the description covers both invocation modes and the 20-item cap, which is enough to call it correctly. Only minor gaps remain (ordering, whether closed tickets are included), and no output schema exists to make return-value details necessary.

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% and the schema already says ticket_id is the internal ID, so the baseline is 3. The description goes further by contrasting it against the customer-facing ticket number with a concrete example (#12345), which is exactly the confusion this parameter invites.

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?

Names a specific verb (auflisten/abrufen) and resource (Support-Tickets) and explicitly describes the two modes of operation: a capped list of own tickets, or a full single-ticket thread when ticket_id is passed. Sibling read tools (close_support_ticket, reply_to_ticket, create_support_ticket) are writes, so this read-only surface is easy to separate.

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?

The description clearly states the condition that selects each mode: omit ticket_id to list, pass ticket_id to get the full thread. No explicit 'when not to use' or named alternative tool is given, but the branch logic is unambiguous.

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