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

The readOnlyHint annotation already establishes that this is a safe, non-mutating read, so the description only needs to add context. 'Across all groups' hints at default scope, but nothing is said about pagination behavior, result ordering, or whether the groupId filter narrows that default scope.

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, which is appropriate for a read-only list tool. It is arguably too terse to be maximally useful, but there is no wasted wording.

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 six-parameter, paginated, read-only listing tool with no output schema, the definition is minimally sufficient: safety comes from annotations and parameter detail from the schema. What is missing is any statement of return shape, default page sizing, or how the filters interact.

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 schema itself carries unusually rich detail (comma-separated type values, timezone-aware inclusive date semantics, UUID format). The description contributes no parameter meaning beyond that, 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?

States a clear verb ('List') plus resource ('deployment history') and adds a scope qualifier ('across all groups') that separates it from the per-deployment siblings like lexq_deploy_detail and lexq_deploy_live. It does not, however, distinguish itself from adjacent list-style tools such as lexq_history_list or lexq_deploy_overview.

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 when-to-use guidance, no mention of when to prefer lexq_deploy_detail / lexq_deploy_live / lexq_history_list, and no prerequisites. The agent must infer the intended context from the name alone.

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