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 covered. The description's added value is the enumeration of returned fields, which compensates for the absent output schema, but it says nothing about ordering, pagination limits, or result volume.

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?

Two short sentences, front-loaded with the action and followed by the useful return-field summary. Nothing is padded or redundant.

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 8 optional parameters and no output schema, listing the returned fields is a meaningful completeness contribution. However, guidance on combining filters, default paging behaviour, or how to retrieve full details after finding a trace is missing for a tool of this breadth.

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%, including detailed semantics for startDate/endDate (tenant time zone, inclusive whole days) and the status enum, so the schema carries the parameter burden. The description adds no filtering or pagination meaning beyond it, making the baseline 3 correct.

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 policy execution history') and enumerates the fields returned (trace ID, group, version, status, match result, latency). That is clear enough to separate it from a detail fetcher, but it never contrasts itself with siblings like lexq_history_get or lexq_history_stats.

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 or when-not-to-use guidance, and no mention of the closely related siblings (lexq_history_get for a single record, lexq_history_stats for aggregates). The agent must infer that this is the paginated, filterable list endpoint purely from the name.

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