directory_get_group

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

The description adds the required permission (Group.Read.All) and enumerates return fields, which is helpful beyond the readOnly/idempotent annotations. However, it fails to address the max_results parameter in the schema, which suggests member return and conflicts with the stated distinction from membership tools.

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?

Two sentences that are front-loaded with the core action and properties, followed by usage guidance and permission. No wasted words.

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 operation, the description covers purpose, alternative, and permission. However, the inclusion of max_results in the schema without explanation is a notable gap that prevents full completeness; an agent would not know whether to pass it or expect member data.

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?

The schema already provides full descriptions for both parameters (GUID and max members to return), so the description adds no additional parameter-level meaning. The baseline of 3 applies due to high schema coverage, but the description also doesn't clarify the apparent max_results conflict.

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 clearly states the tool retrieves details for a single Entra ID group by ID and lists specific properties (display name, description, type, email, visibility, creation date). It also distinguishes itself from the sibling directory_list_group_members, which returns membership.

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?

It explicitly states 'Use when a group id is already known and its properties matter rather than its membership' and directs to directory_list_group_members for membership. This is clear when-to-use guidance with an alternative.

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