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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds one real piece of behavioral context beyond that — the operation is scoped to DRAFT versions — but says nothing about irreversibility, whether the rule must be disabled first, or what happens to references/history after deletion.

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 short sentence with zero filler and the key constraint front-loaded. It is efficient, though the terseness is close to the edge where brevity becomes under-specification.

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 three-parameter delete with fully documented schema and destructiveness already flagged by annotations, the description covers the essential scope. It still leaves gaps for a destructive mutation: no note on irreversibility, on failure modes for non-draft versions, or on any post-delete state change, and there is no output schema to cover results.

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 all three UUID identifiers documented in the schema, so the baseline is 3. The description adds no meaning about how groupId, versionId, and ruleId relate (e.g. that the rule must belong to the given group and version), leaving that inference to the agent.

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 (Delete) and resource (a rule), plus a scope qualifier ('from a DRAFT version') that distinguishes it from the rule-mutating siblings like lexq_rules_update and lexq_rules_toggle. It does not explicitly name any sibling, so it falls short of a 5, but an agent can identify the operation without opening the schema.

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 'DRAFT version' qualifier implicitly tells the agent when this tool is applicable and implies it cannot be used against published versions, which is useful when-to-use guidance. However, no alternatives are named (e.g. versions_delete, rules_update to remove a rule config differently) and no prerequisites such as required permissions or version state transitions are given.

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