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

Annotations already cover readOnly, idempotent, destructive=false and openWorld, so the safety profile is fully declared. The description adds genuine behavioral context beyond that: the result is aggregated counts, no ticket records are returned, and criteria are optional. It does not discuss pagination or scale limits, but for an aggregate read those gaps are minor.

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 compact two-part sentence that front-loads the payload (per-status counts + total) and then the optional narrowing mechanism. The embedded inline example makes the second half dense, but every element earns its place.

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 one optional parameter, full schema coverage, an output schema and safety annotations, the description supplies everything needed to invoke it correctly, including the non-obvious search-option field IDs. The example criteria omits the 'link' element and the option-ID list is illustrative rather than exhaustive, which keeps it just short of 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 coverage is already 100%, yet the description still adds real meaning by supplying concrete Ticket search option IDs (80=entity, 4=requester, 5=technician, 7=category) that appear nowhere in the schema, plus a worked criteria example and a pointer to glpi_search for the same shape.

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+output shape: counts of tickets broken down by the five named statuses plus a total. The clause 'without listing the tickets' explicitly distinguishes it from the many sibling list tools (glpi_list_tickets, glpi_list_my_tickets), so an agent can tell them apart without opening schemas.

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?

Makes clear this is the tool for aggregate counts rather than enumeration, and shows how to narrow scope with a concrete entity example. It also points at glpi_search for the criteria shape, which helps reuse. It stops short of naming an explicit alternative or a when-not condition beyond the implicit 'not listing' contrast.

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