ise_ers_search_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 of behavioral disclosure. It doesn't state whether this is a read-only operation (implied by 'search/filter' but not explicit), how pagination interacts with filtering, whether the search returns all matching groups or requires exact matches, or what happens when the filter is malformed. For a tool with zero annotation coverage, this is a meaningful gap.

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 a single concise sentence that earns its place. It's brief and front-loads the purpose. However, given the tool's parameter complexity and the gap in schema coverage, some additional detail would be warranted, so it's slightly under-specified rather than perfectly concise.

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 search tool with 5 parameters, 0 required, no output schema, and no annotations, with only 20% schema coverage. The description does not explain the filter expression format, pagination semantics, or return behavior. The deployment parameter is well documented in the schema, but the core 'filter' capability that defines this tool remains vague. For a search tool, the description should explain what filtering can do — this is a significant completeness gap.

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 20% — only the 'deployment' parameter has a description; 'page', 'size', 'sort', and 'filter' are undocumented in the schema. The description mentions 'ERS filter expressions' which gives some context for the 'filter' parameter, but it doesn't explain the expression syntax, default page/size behavior, or sort format. The description adds some value for 'filter' but doesn't compensate for the 80% coverage gap. The 'deployment' param is well-described in the schema itself.

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 'Search/filter Endpoint Identity Groups with ERS filter expressions' uses a specific verb (search/filter) with a clear resource (Endpoint Identity Groups) and mechanism (ERS filter expressions). It distinguishes itself from sibling tools by the 'search' prefix versus list/get, though it shares the pattern with other ise_ers_search_* tools so it doesn't fully differentiate against those.

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 explicit guidance on when to use this vs alternatives. It doesn't explain the distinction from ise_ers_list_endpointgroup (pagination vs filter), from ise_ers_search_endpoint (searching endpoints vs groups), or ise_dc_view_endpoint_identity_groups. The 'search/filter' wording implies usage but provides no exclusions or alternatives, and doesn't explain what ERS filter expressions look like or the tradeoff versus listing.

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