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

No annotation contradiction. The readOnlyHint=true annotation already signals a safe read; the description adds the source-domain context (webhooks and scheduled deployments) which narrows what the agent should expect. This is additive value beyond annotations. However, it does not disclose pagination behavior or return envelope details, but given the annotation carries the safety profile, this is a marginal gap. A strong 4.

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?

One single sentence, zero filler, each word earns its place. The source domain ('background tasks') is front-loaded before the parenthetical detail. Efficient and scannable.

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?

Complete enough for a filtered-list entry-point tool. It explains what data domain it covers (failure logs from two specific sources), and the schema covers all filtering parameters. It does not describe the output structure or return fields, but with no output schema present, the agent can infer log entries from context. Minor gaps only.

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% — all 7 parameters are already described in the schema (status enum, search fields, date format, pagination bounds). The description adds no parameter-level meaning beyond what the schema provides. Baseline 3 is correct 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?

States a specific verb ('List'), resource ('system failure logs'), and the exact domain (background tasks: platform event webhooks, scheduled deployments). Clear and unambiguous. It is a listing tool that differentiates from sibling lexq_logs_get (single log) and lexq_logs_action/bulk_action (mutations) by scope — a list retrieval.

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?

States when to use the tool: to see failure logs from background tasks. While it names two concrete source categories, it does not explicitly exclude alternatives (e.g., when to prefer lexq_logs_get, lexq_history_list, or lexq_deploy_history instead). The naming convention and 'logs' prefix imply the domain, but no explicit when-not guidance is given. Slightly above baseline because the source scope is concrete.

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