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

The readOnlyHint annotation already signals a safe read operation. The description adds minimal behavioral context—it states it lists history with filters, which is consistent with the annotation. It does not disclose pagination behavior or return format, but given the annotation coverage, the description is adequate.

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 description is a single concise sentence with no filler. It front-loads the core purpose (list simulation history) and mentions optional filters, effectively using every word.

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 simple list operation with five optional parameters and no output schema, the description is functional but lacks context on how it differs from similar sibling tools like lexq_history_list. It also doesn't mention pagination defaults or any special behavior beyond what the schema implies.

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%, with every parameter (to, from, page, size, status) already documented. The description only says 'optional filters', which adds no semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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 'List simulation history with optional filters' clearly states the verb (list), resource (simulation history), and scope (optional filters). It distinguishes from sibling tools like lexq_simulation_start, lexq_simulation_cancel, and lexq_simulation_status, which are about actions or status, not listing history.

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 implies this is for browsing past simulations via 'history' and 'optional filters', but does not explicitly name alternatives like lexq_history_list (which might serve a similar purpose) or lexq_simulation_status (for a single simulation's status). No when-not-to-use guidance is provided.

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