get_zpa_scim_group

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

The description merely restates the readOnlyHint annotation. It does not disclose additional behavioral traits such as pagination, filtering, or the nature of the output. For a read-only tool, more context is needed.

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 (one phrase), which is efficient, but it lacks structure and fails to convey essential information beyond the annotation. It is front-loaded but incomplete.

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?

Despite having an output schema and multiple parameters, the description provides minimal context. It does not explain the required action parameter, the need for idp_name when listing, or any usage nuances. The description is insufficiently complete.

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?

The input schema has 100% description coverage for all 5 parameters, so the schema already provides meaning. The description adds no extra parameter context, earning a baseline score of 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 states 'Manage ZPA SCIM Groups (read-only)', which clearly identifies the resource and indicates it's a read operation, differentiating it from write tools. However, 'Manage' is somewhat vague; 'Get' or 'List' would be more precise.

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 on when to use this tool versus alternatives. Sibling tools like get_zpa_scim_attribute suggest related functionality, but the description provides no context for selection.

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