ise_ers_list_identitygroup

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states 'Paginated.' which hints at paging behavior without specifics like page size limits, ordering, or error conditions. The deployment selection behavior is documented in the schema param, not the description. It's a safe read operation (List) but gives minimal extra behavioral context beyond the name.

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 description is extremely concise at just two phrases in one line. Every word earns its place, though it's arguably under-specified rather than lean in a way that adds value. It's front-loaded with purpose then the single behavioral note about pagination.

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?

The tool has 3 params, no output schema, and no annotations, so the description carries significant burden. It provides only purpose and pagination note. For a listing tool that returns an array of identity groups, it gives no sense of result count expectations, ordering, or relationship to the deployment parameter. The pagination behavior with page/size is referenced only implicitly. This is adequate but leaves meaningful gaps.

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 33% (only 'deployment' has a description; 'page' and 'size' rely on names/defaults). The description adds nothing beyond the schema; 'Paginated' loosely maps to page/size semantics. With only partial coverage, the description could compensate but doesn't detail page/format expectations, earning the baseline 3.

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 'List all Identity Groups. Paginated.' uses a specific verb (List) and resource (Identity Groups), clearly indicating the operation. It distinguishes from sibling 'get' and 'search' variants of identitygroup, though it doesn't explicitly contrast with them. It's a clear purpose but could slightly improve with mention of scope/fields returned.

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?

No guidance is provided on when to use list vs the sibling get_identitygroup or search_identitygroup tools, nor when to use list_identitygroup vs list_endpointgroup. The pagination note is implicit, and the deployment parameter guidance lives in the schema, not the description. No explicit when/when-not guidance exists.

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