get_nested_group_members

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

With no annotations, the description carries the full burden and does well: it discloses the server-side LDAP_MATCHING_RULE_IN_CHAIN evaluation, handling of deep/cyclic nesting without client recursion, base-DN confinement, and truncation via 'truncated'. It omits read-only confirmation, permission requirements, and latency/cost expectations.

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?

Front-loaded with the core purpose, followed by mechanism, scope, and return shape; the example earns its place. Slightly wordy in the mechanism sentence but no filler.

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 tool with no output schema, the description covers return fields (dn, sAMAccountName, displayName, type), truncation signaling, and scope boundaries. What remains unstated is permission requirements and what happens when the group name does not resolve.

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 already documents that group_name is a sAMAccountName, so the description adds little beyond the schema. The example reinforces the expected value shape but introduces no new semantics such as DN vs name forms or error behavior for unresolved groups.

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 all direct and nested members of a group') and the qualifier 'nested' implicitly distinguishes it from the sibling get_group_members. It never names that sibling explicitly, so the differentiation must be inferred rather than read.

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 example shows a canonical call and the description bounds results to the base DN and max_list_results, which implies when the tool fits. However, it never says when to prefer this over get_group_members or get_user_groups, leaving the agent to infer the distinction from the word 'nested'.

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