Get Group

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

readOnlyHint=true and an output schema already cover safety and return shape, so the description's main added value is the 'exact match' constraint, which tells the agent no wildcards or partial matching are accepted. It says nothing about not-found behavior, cn ambiguity, or what the domain parameter changes.

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?

A single front-loaded sentence with no filler; the key constraint (exact match) is attached directly to the identifier explanation.

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 read-only lookup with an output schema, the description covers the core input semantics adequately. The unexplained domain parameter and absent not-found/ambiguity behavior keep it from being 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?

Schema description coverage is 0%, so the description must compensate; it does add real meaning for 'identifier' (sAMAccountName or cn, exact match). However, the optional 'domain' parameter is entirely undocumented in both schema and description, leaving a significant gap.

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?

States a specific verb and resource ('Get a single AD group') and the 'single' qualifier implicitly contrasts with list-style siblings like find_groups. It never names a sibling explicitly, so an agent must infer the get-vs-find split itself.

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 'exact match' note implies this is for precise lookups rather than fuzzy searching, which hints at when to prefer find_groups. There is no explicit when-to-use/when-not or named alternative such as get_by_dn.

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