list_groups

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the default page bound, the return envelope, and the note that 'truncated' is measured rather than guessed, which tells the agent it can trust the flag.

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?

Front-loaded '[READ]' tag, then compact Args and Returns sections with no filler. Every line carries information, though the Args/Returns formatting is slightly verbose for two parameters.

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 present, the description carries the return format itself, including the envelope keys and the truncation flag, and documents both parameters despite zero schema coverage. It is close to complete for a simple list tool, lacking only detail on group object fields and how to fetch subsequent pages.

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 0%, so the description must compensate and largely does: it explains max_results as a page bound with default 200 and clarifies target as an IdP target name from config that should be omitted for the default. It does not define target's valid values or how paging continues, keeping it below a 5.

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 '[READ] Groups in the realm' opening, reinforced by the name list_groups, makes the resource and operation clear enough to distinguish it from group_members or list_users. However, it states the resource as a bare noun phrase rather than an explicit verb like 'list', so it stops 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 guidance on when to use this tool versus siblings such as group_members or list_users, and no prerequisites or exclusions are stated. The only context is the '[READ]' tag, which describes operation type rather than usage conditions.

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