get_ad_user_or_group

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds little behavioral context beyond the read nature, and because it operates on a known ID it does not disclose failure behavior (e.g., what happens for an unknown ID). With annotations carrying the load, a 3 is appropriate.

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 or redundancy. It is appropriately short for a simple lookup tool, though it errs toward minimalism rather than earning full marks.

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?

The tool is simple (one param) and an output schema exists, so return values need not be explained. The main gap is the absence of routing information relative to the search sibling and any note on identifier sourcing, leaving the definition adequate but not fully rounded.

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% for the single ad_id parameter, and the input schema already documents it as 'AD user or group ID'. The description adds no syntax or format detail beyond the schema, so the 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 states a clear verb (Get) and resource (AD user or group) scoped to 'a specific' item, which distinguishes it from the plural search_ad_users_or_groups and list_ad_* siblings. The phrase 'detailed information' is somewhat vague about what is actually returned, but the core purpose is unambiguous.

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 explicit when-to-use guidance and no mention of the sibling search_ad_users_or_groups that an agent would logically use first to obtain the ad_id. The word 'specific' weakly implies a known identifier is required, but the routing condition is left to inference.

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