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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, yet the description adds genuinely non-inferable behavior: articles are returned in order, attachments are named but NOT downloaded, and bodies are truncated at 6000 characters. The truncation limit is exactly the kind of trait an agent must know before trusting the output.

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?

A single dense run-on sentence plus the raw endpoint, front-loaded with the resource and scope and immediately followed by the two caveats an agent cares about (truncation, attachment names only). No filler.

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?

No output schema exists, so the description carries the return-value burden and it does so by enumerating returned fields, ordering, and truncation. Combined with the annotations covering the safety profile, nothing needed to call it correctly is missing.

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?

Only one required integer parameter with a 100% covered schema description ('Zammad ticket id.'). The description reinforces that the id scopes to 'one ticket' but adds no format or constraint detail beyond the schema, 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?

Specific verb+resource: lists all articles of a single ticket, and enumerates exactly which fields come back (sender, type, internal flag, from/to/cc, subject, body, attachment names). The phrase 'of one ticket' plus the explicit contrast with zammad_get_ticket_article makes it distinguishable from siblings without opening a 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?

Gives an explicit routing rule: 'Long bodies are cut at 6000 characters; use zammad_get_ticket_article for the full text.' That tells the agent when to switch tools, though it offers no guidance distinguishing this from zammad_get_ticket or zammad_list_tickets.

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