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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint true), so the bar is lower. The description still adds real behavioral context: without `fields` you get only a short summary, and it discloses the underlying endpoint GET /api/groups. Pagination/limit behavior is left to the schema.

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?

Two compact sentences: the resource definition is front-loaded, followed by the most decision-relevant parameter behavior and the endpoint. No sentence is filler.

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 five-parameter listing tool with full schema coverage, annotations, and no output schema, the description gives enough to call it correctly. It hints at the short-summary default, though it could say more about what the summary contains or how filtering combines.

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 every parameter is already documented, establishing a baseline of 3. The description only restates the `fields` parameter pattern that the schema already explains, adding no extra semantics for name, limit, group_ids, or workspace_id.

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 and resource ('list resource groups') and parenthetically defines what a group is with concrete examples (Staff, Rooms, Vehicles), which separates it conceptually from labels and resources. It does not explicitly name sibling tools like list_label_groups to disambiguate, so it falls short of a 5.

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?

There is no statement of when to use this tool versus list_resources, list_labels, or list_label_groups, and no prerequisites or exclusions. The note about passing `fields` is a parameter tip, not usage guidance.

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