list_ad_containers

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the meaningful behavioral context that this is the API equivalent of the Horizon Console OU picker, i.e., a discovery step feeding a provisioning flow. It does not discuss pagination or result size, but the output schema exists.

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 purpose, then downstream usage. The long parenthetical naming both create_desktop_pool and create_rdsh_farm paths is dense but earns its place by preventing a wrong-parameter mistake. Slightly verbose but no filler sentences.

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?

A single-parameter read tool with full schema coverage, an output schema, and annotations covering safety. The description covers the remaining risk (where the rdn is consumed and where it is not), which is exactly the gap needed for correct end-to-end use.

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?

One parameter (domain_id) with 100% schema description coverage, and the schema already says 'obtain from list_ad_domains'. The description's mention of ad_container_rdn refers to another tool's parameter, so it adds no meaning beyond the schema for this tool's own input. 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?

States a specific verb and resource ('List AD containers (OUs)') plus scope ('available in a domain'), and clarifies the OU concept to separate it from list_ad_domains or search_ad_users_or_groups. An agent can identify exactly what this returns.

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?

Explicitly tells the agent where the result goes: the rdn becomes ad_container_rdn in create_desktop_pool's customization_settings (or create_rdsh_farm's automated_farm_settings.customization_settings), and explicitly warns it is NOT provisioning_settings. That is precise downstream routing plus an exclusion.

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