ise_ers_get_endpointgroup

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

No annotations are provided, so the description carries full burden of behavioral disclosure. The description is a simple read-ish statement ('Get') with no details about permissions, response shape, pagination, or error behavior. However, the tool name and description clearly indicate a fetch-by-ID operation which is inherently low-risk; still, there is no added behavioral context beyond the obvious.

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 sentence, which is efficient. However, the deployment parameter in the schema has detailed documentation while the description adds nothing about it. The sentence is minimal but not wasteful.

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 simple single-object fetch tool with 1 required parameter (id) documented in the name, the description is arguably sufficient. However, there is no output schema, no annotations, and the description does not clarify what the return value looks like or whether the endpointgroup concept differs from identitygroup (a sibling tool). Given the low complexity, this is borderline adequate.

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 coverage is 50%: the id parameter has no description in the schema, and the description does not explain it either. The deployment parameter's meaning is well documented in the schema itself. The description adds nothing about parameter semantics; the id meaning can only be inferred from the tool name.

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 'Get a single Endpoint Identity Groups object by ID' which conveys a clear verb+resource+scope. It distinguishes from sibling list/search tools (ise_ers_list_endpointgroup, ise_ers_search_endpointgroup) by emphasizing singular fetch-by-ID. It does not name alternatives but the sibling differentiation is implicit.

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 given about when to use get vs list or search variants. The tool name pattern strongly implies use when you have a known ID, but the description does not explicitly state this or mention alternatives like search_endpointgroup for name-based lookup. Sibling tools exist that could perform similar functions, but no distinctions are drawn.

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