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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds little beyond that: it does not say what happens for an invalid or empty ticket, how pagination defaults behave, or the shape of the enriched names, so it mostly restates the read operation the annotations already declare.

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 tight sentence that front-loads the resource and lists the enrichment fields. It earns its place, though the parenthetical field list adds modest value rather than routing the agent to alternatives.

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 a full input schema, an output schema and rich annotations, the core contract is already implied. The description leaves out the guidance an agent still needs: when to choose this over sibling listing tools and what the enriched fields mean operationally.

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 description coverage is 100%, so all four parameters (ticketId, range, fields, format) are already documented in the schema. The description adds no syntax, defaults, or format details beyond what the schema provides, so it sits at the baseline.

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 and resource ('List tasks (to-do items) for a ticket') and enumerates the enriched fields returned (user_name, tech_name, tech_group_name). It is distinguishable from mutation siblings like glpi_add_ticket_task, but does not explicitly differentiate from the analogous list tools for changes and problems.

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?

No guidance on when to use this rather than glpi_list_timeline, glpi_get_ticket, or the change/problem task variants, and no stated preconditions such as that the ticket must exist. Usage is only implied by the name and the required ticketId.

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