account_groups_get

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

The description 'Fetch' aligns with the readOnlyHint annotation. However, it does not add behavioral context beyond that, such as error behavior on missing group or authentication requirements. With annotations covering the core trait, the description adds only marginal value.

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 states the purpose directly. No filler or redundancy.

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 get operation with an output schema, the description is largely sufficient. It could mention that this is account-level (distinct from workspace groups), which it does. No major gaps.

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% (parameter 'id' described as 'Group ID'). The description adds no further meaning. Baseline of 3 is appropriate as the schema already documents the parameter adequately.

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 'Fetch an account-level SCIM group' uses a specific verb ('Fetch') and resource ('account-level SCIM group'), clearly distinguishing it from sibling tools like account_groups_list or account_groups_create.

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 tool versus alternatives (e.g., list, create, delete). The description does not state prerequisites or when not to use it, leaving the agent to infer from the tool name.

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