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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is fully carried by structured data. The description adds no behavioral context of its own — no note on permission requirements, on whether the update is partial or full, or on what happens to fields omitted from the payload. It does not contradict the annotations.

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 front-loaded sentence with zero padding, so nothing needs trimming. The problem is under-specification rather than verbosity — it is too sparse rather than too long.

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 destructive, open-world mutation whose payload is an unconstrained free-form object, the description is far too thin. An output schema exists so return values need no explanation, but the description should still cover valid fields, permission needs, and partial-update semantics.

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 nominally 100%, but the "input" parameter is an additionalProperties:{} free-form object described only as "Fields to update", so the schema does not actually tell the agent which ticket fields are settable. The description says nothing to compensate, leaving the payload contract undefined.

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 ("Update an existing ticket") and keys it on ID, which cleanly separates it from glpi_create_ticket and glpi_get_ticket. However, it does not name or contrast any sibling such as glpi_update_change or the ticket sub-resource tools (glpi_add_followup, glpi_add_solution).

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?

There is no guidance on when to use this tool versus alternatives. A ticket can also be modified through glpi_add_followup, glpi_add_solution, glpi_add_ticket_user, glpi_add_ticket_task, and glpi_update_ticket_validation, and nothing tells the agent when a general update is the right call.

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