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 covered. The description adds only that pagination and dropdown expansion are 'optional', which is already visible in the schema; it does not state default page size, whether omitting 'range' returns everything or a first page, or any instance-size limits.

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 no filler; every clause maps to a real capability of the tool. It is efficient, though the word 'all' sits slightly awkwardly next to 'optional pagination' without clarifying the default result size.

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?

An output schema exists, so return values need not be explained, and the schema fully documents the four optional parameters. The remaining gap is the ambiguous default: an agent cannot tell from the description whether calling with no 'range' enumerates every user or only the first page, which is material for a listing tool.

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% and the two enum parameters are fully documented with defaults and output implications, so the schema carries the semantic load. The description adds no format examples, range syntax, or interaction between 'range' and 'fields'/'expand_dropdowns' beyond what is already there. 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?

Clear verb+resource ('List all users') with the two optional behaviors (pagination, dropdown expansion) named up front. It does not differentiate itself from siblings like glpi_get_user, glpi_search_user_by_email, or glpi_list_groups, leaving the agent to infer the boundary from the name alone.

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 gives no when-to-use guidance, no prerequisites, and never names an alternative such as glpi_get_user for a single record or glpi_search_user_by_email for lookup by email. The only usage signal is the word 'List', which the tool name already conveys.

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