manage_security_groups

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

Annotations indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false, which already inform the agent about mutation capabilities and potential data loss. The description adds minimal behavioral context beyond this - it mentions 'access control' implications but doesn't elaborate on authentication needs, rate limits, or specific destructive consequences. No contradiction with annotations 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?

The description is a single, efficient sentence that front-loads the core purpose. It avoids unnecessary elaboration while covering the key aspects of what the tool manages. However, it could be slightly more structured by separating scope elements for better readability.

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 complex tool with 6 parameters, destructive operations, and no output schema, the description is minimally adequate. It identifies the resource and general scope but lacks details about error conditions, response format, or operational constraints that would help the agent use it correctly. The annotations provide safety information, but more context about this multi-action tool would be beneficial.

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?

With 100% schema description coverage, the input schema already documents all 6 parameters thoroughly. The description adds no parameter-specific information beyond the generic 'including group creation, membership, and security settings' which loosely maps to action types but provides no additional syntax, format, or constraint details. Baseline 3 is appropriate when schema does the heavy lifting.

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's purpose: 'Manage Azure AD security groups for access control, including group creation, membership, and security settings.' It specifies the resource (Azure AD security groups) and the scope of operations (creation, membership, security settings). However, it doesn't explicitly differentiate from sibling tools like 'manage_m365_groups' or 'manage_distribution_lists' which might handle similar group management tasks.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when-not-to-use scenarios, or refer to sibling tools like 'manage_m365_groups' for comparison. The agent must infer usage from the generic 'manage' term and parameter schema alone.

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