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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description only needs to extend that. It adds that rows omit group attributes and that results are capped at 100 groups — useful operational context. It stops short of describing pagination mechanics (offset/limit interplay) or whether counts are exact.

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?

The core scope and default ordering are front-loaded, and the sibling redirects are compact. The opening sentence is dense with parentheticals and could be split, but nothing is wasted.

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 read-only list tool with 7 optional params and no output schema, it covers default ordering, result cap, which fields are present versus absent, and where to go for attributes and members. An agent can call this correctly and know when to switch tools.

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 coverage is 100% and each parameter is documented in the schema, including sort values, type normalization ('ParentCompany' == 'parent_company'), and offset paging. The description restates the filter trio and default ordering but adds no syntax beyond the schema, so the baseline 3 applies.

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) and resource (groups), defines what a group is versus clusters ('not clusters Dregs detected'), and names the returned fields (type, member identity count, default lastTrackedAt ordering). This lets an agent separate it from get_group, list_identities, and the sibling dashboards 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?

Explicitly routes the agent: 'call get_group' for attributes and 'call list_identities with its id and type' for members. It also enumerates the three filter modes (type, term, identity) that select this tool over a general list.

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