featured_fields_replace_ad_groups

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

With no annotations, the description carries the full burden. It explicitly discloses the destructive behavior ('delete all existing active directory groups') and the required license, which are critical for an agent to safely invoke the tool. It doesn't detail response format, but the core risks are covered.

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?

The description is well-structured with a clear summary, a warning note, license info, endpoint URL, and an example. Each section adds useful context without excessive verbosity.

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 mutation tool with no output schema, the description covers the essential operational aspects: what it does, the destructive side effect, license requirements, and an example. It is complete enough for an agent to understand the tool's purpose and risk profile.

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?

Although the schema itself has rich descriptions for each field, the description adds an example request body that illustrates the exact structure and usage of the nested fields. This provides practical meaning beyond the schema definitions.

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 specific action ('Replace') and a specific resource ('featured active directory groups and organizational units'). It clearly distinguishes from sibling tools like featured_fields_replace_hosts and featured_fields_replace_users, which target different resource types.

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 description provides clear context by specifying the resource type and including a prominent deletion warning. It does not explicitly name alternatives, but the context makes it obvious when to use this tool versus siblings.

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