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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds essentially nothing beyond that: it does not mention pagination defaults (page 0, size 20, max 100), result ordering, time windowing, or what a deployment record contains. For a list endpoint with no output schema, that leaves real behavioral gaps.

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?

The single sentence is front-loaded and free of filler, which is good, but it is under-specified rather than concise. The space saved is spent by the agent on guessing scope, ordering, and pagination behavior.

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 six optional parameters, no output schema, and no annotations beyond the safety hints, the description should at least note default pagination and result ordering. Instead it stops at the resource name, leaving the agent to infer how results are paged and sorted from the input schema alone.

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 six parameters (page, size, types, startDate, endDate, groupId) are already fully documented in the schema, including enum-like values for types and timezone semantics for the dates. The description adds no parameter meaning; 'across all groups' arguably sits in mild tension with the existence of a groupId filter parameter. Baseline 3 applies when the schema does the heavy lifting.

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?

The description states a specific verb and resource ('List deployment history'), so the agent knows this is a read operation returning past deployments rather than current state. However, it gives no differentiation against the many nearby siblings such as lexq_deploy_detail, lexq_deploy_overview, or lexq_history_list, so the agent cannot tell from the text alone which of these to pick.

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 when-not-to-use guidance, and no naming of an alternative tool. The phrase 'across all groups' hints at a broad-scope listing (as opposed to per-group queries), but that implication is never stated as a selection rule.

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