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 contributes the payload shape (condition tree plus action definitions), which matters because no output schema exists, but says nothing about not-found behavior, permission requirements, or version scoping semantics.

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 front-loaded sentence with the resource and returned content in immediate view; nothing is padded or repeated. It is efficient, though the terseness leaves no room for the scoping detail an agent would benefit from.

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 no output schema, the description partially discharges its burden by naming the two major return components. However, for a tool requiring a three-level identifier path (group, version, rule) with no explanation of that hierarchy or of failure modes, the definition is only minimally sufficient.

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 three UUID parameters are documented in the schema and the baseline of 3 applies. The description adds no meaning beyond the schema: it never explains that ruleId is resolved within a groupId plus versionId hierarchy, which is the one piece of semantic context the schema cannot express.

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 names a specific verb and resource ("Get full rule detail") and enumerates what the detail contains ("condition tree and action definitions"), which distinguishes it from lexq_rules_list. It stops short of naming the sibling it supersedes, so the differentiation is inferred rather than stated.

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?

Use is only implied: an agent can infer this is the drill-down companion to lexq_rules_list because it returns full detail rather than summaries. There is no explicit when-to-use, no mention of prerequisites such as needing groupId/versionId resolution first, and no guidance on when lexq_rules_update or lexq_groups_get would be the better call.

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