ise_ers_list_endpointgroup

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior ('Paginated') and implies a read-only retrieval, but doesn't state default page size, what fields are returned, rate limits, or authorization requirements. For a listing tool, stating pagination is helpful but minimal behavioral context is missing.

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?

At just two sentences ('List all Endpoint Identity Groups. Paginated.'), every word earns its place. It's front-loaded with the core purpose and adds one essential behavioral trait (pagination) without padding.

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?

This is a simple list tool with 3 optional parameters, no output schema, and no nested objects. The description correctly identifies the resource and pagination. While it could mention default page/size values (100 items by default) and noting it retrieves the full collection, the complexity is low and the description is adequate for an agent to invoke it correctly.

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 only 33% — only 'deployment' has a description in the schema; 'page' and 'size' are bare. However, their names are largely self-documenting given the 'Paginated' note. The description's mention of pagination adds context to the 'page' and 'size' params, and the deployment description is rich. The description compensates reasonably despite low schema coverage.

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 'List all Endpoint Identity Groups. Paginated.' This clearly identifies the verb (List), resource (Endpoint Identity Groups), and scope (all). It distinguishes from sibling list tools like ise_ers_list_networkdevice or ise_ers_list_sgt by naming the specific resource. However, it doesn't explicitly differentiate from closely related siblings like ise_ers_list_identitygroup or ise_dc_view_endpoint_identity_groups.

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 pagination mention implies a listing context, but there's no explicit 'use when' guidance. It doesn't contrast against alternatives like ise_ers_search_endpointgroup (for filtered lookup) or ise_ers_get_endpointgroup (for single fetch). The deployment parameter references ise_list_deployments, offering indirect guidance, but no explicit when-to-use vs. alternatives is provided.

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