provider_get_group

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and the annotations title already carries the exact endpoint path "GET /cloudapi/1.0.0/groups/{groupUrn}", which the description simply repeats. Nothing new is disclosed about return behavior, not-found handling, or scope of visibility.

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?

Only two short lines with the purpose front-loaded, which is efficient. But the second line duplicates the annotation title verbatim rather than earning its place by adding information.

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 one-parameter read-only fetch with full annotation coverage and no output schema, the definition is minimally sufficient to invoke correctly. It still lacks any hint about the response shape or how a group URN is discovered, which would be the useful additions.

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 100% and the single parameter is documented as "groupUrn (path)", so the schema carries the load. The description adds no meaning about the URN format or where the value is obtained, leaving it at the baseline.

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 a specific verb and resource ("Get a specified group"), which is clearer than a tautology. However, it never distinguishes this single-item fetch from the many related siblings such as provider_query_groups, provider_get_user, or provider_get_role, so the agent must infer it fetches exactly one group by URN.

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?

There is no guidance on when to use this versus provider_query_groups (listing) or provider_query_group_users (membership). No prerequisites, permissions, or error conditions (e.g., group not found) are mentioned, so all usage decisions are left to inference.

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