ise_dc_view_endpoint_identity_groups

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

No annotations are provided, so the description carries the full behavioral burden. While the '[Report]' tag implies read-only, the description does not explicitly state it's non-mutating, nor does it describe pagination/limit behavior, default filtering semantics, deployment targeting requirements, or how the days_back time column works. The deployment parameter's behavior is only explained in the schema, not the description.

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 concise, a single sentence that states purpose, and the column list is useful. It is efficiently sized. Slight improvement possible by being more explicit about read-only nature and sibling differentiation, but it earns its place.

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 report tool with good schema coverage and no output schema, the description provides the filterable columns which is valuable. However, the tool is one of many endpoint-identity-related sibling tools, and the description doesn't clarify what distinguishes this report view from the ERS identity group tools or from ise_dc_view_endpoints_data. The behavioral transparency gap (no explicit read-only statement, deployment targeting ambiguity) also reduces completeness.

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 the schema documents all 7 parameters thoroughly (limit defaults, filter operators, deployment name/slug/number format). The description adds the list of filterable columns (ID, NAME, DESCRIPTION, CREATED_BY, CREATE_TIME, UPDATE_TIME, STATUS), which is genuinely useful beyond the schema by telling the user which columns exist and can be filtered/sorted. This adds meaning the schema does not provide.

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 clearly states this is a report tool that provides details of endpoint identity groups, and lists the filterable columns. It identifies the resource (endpoint identity groups) and mode (report/view). However, it does not explicitly distinguish this from siblings like ise_ers_list_identitygroup or ise_dc_view_endpoints_data, though the '[Report]' prefix and view naming partially separate it.

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 description signals this is a read/report operation and lists filterable columns, implying it's for querying endpoint identity groups. However, it does not explicitly state when to use this versus the ERS-based identity group tools (ise_ers_list_identitygroup, ise_ers_get_identitygroup) or other DC view tools. No exclusions or alternatives are mentioned.

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