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

The annotation readOnlyHint=true already declares it's a read operation, so the description is not burdened with that. The description adds behavioral context beyond annotations: it specifies the scope (tenant-wide) and ordering (priority ASC). However, it does not mention pagination, result size limits, or whether it returns all fields or just summaries. With annotations covering safety, a 3 is appropriate.

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 no filler. It leads with the verb and resource, then adds the two qualifiers parenthetically. Every word earns its place; it is an exemplary concise structure.

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 zero-parameter list operation with no output schema, the description fully covers what an agent needs to know: it lists all policy groups, applies to the entire tenant, and returns them in ascending priority order. There are no missing details that would prevent correct invocation.

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?

There are zero parameters, so per the rubric the baseline is 4. The description adds no parameter information, but none is needed. The schema is trivial (empty object) and the description already explains the tool's behavior, so nothing is lacking.

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 states the verb 'List' and resource 'policy groups' clearly, and adds specific qualifiers 'tenant-wide' and 'priority ASC' that distinguish it from other group operations like create, get, or reorder. The title reinforces this. An agent can immediately understand what this tool does and how it differs from siblings.

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 purpose implies usage (enumerate groups), but the description does not explicitly state when to use this tool versus alternatives such as lexq_groups_get for a single group or lexq_groups_update for modifications. No exclusions or alternative routing are given, so guidance is only implied by the verb 'List' and tool name.

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