identity_get_organization_groups

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

Annotations already declare readOnly, idempotent, non-destructive, so those traits add no value here. The description contributes beyond them with a role access matrix (platform operator, org owner allowed; org member and non-whitelisted service accounts denied), which materially affects whether a call will succeed, and with the deprecation status. It stops short of stating pagination or default page size behaviour.

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 deprecation warning is correctly front-loaded, which is good. But the markdown table arrives as escaped HTML entities, the endpoint string is repeated at the start and end, and the access-policy block is verbose for a read-only deprecated lookup.

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?

Given 100% schema coverage, read-only annotations, and no output schema, the definition covers safety and authorization adequately. The gaps are pagination semantics and an explicit pointer to the sibling tool or a removal timeline, which matter because the tool is deprecated and paged.

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 all four parameters (orgId, groupId, pageLimit, pageStart) are already documented in the schema. The description adds no param-level detail such as whether groupId narrows results or how pageStart interacts with pageLimit; baseline 3 applies.

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 opens with a retained verb+resource label ('Get Organization Groups') and clarifies scope as groups of a specific organization, backing it with the underlying endpoint GET /csp/gateway/am/api/orgs/{orgId}/groups. It does not name the closest sibling (identity_search_org_groups), so differentiation from alternatives relies on the agent inferring 'list all' versus 'search'.

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 explicit deprecation notice plus a replacement path is genuinely useful 'use something else' guidance, which is rare. However, the replacement is a raw REST endpoint rather than a sibling tool name, so an agent cannot map it to identity_search_org_groups or provider_query_groups directly, and there is no guidance on when this tool remains the correct choice.

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