manage_m365_groups

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

Annotations already indicate this is a destructive, non-idempotent, non-read-only tool. The description adds minimal context by mentioning 'shared resources like mailbox, calendar, and files,' which hints at the scope of changes. However, it doesn't elaborate on permissions needed, rate limits, or specific behavioral traits beyond what annotations provide.

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 without unnecessary details. It's appropriately sized for a tool with comprehensive schema documentation, earning its place by summarizing the tool's scope.

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?

Given the tool's complexity (7 parameters, destructive operations) and lack of output schema, the description is minimally adequate. It covers the high-level purpose but doesn't address behavioral details like error handling or response formats, which would be helpful given the annotations indicate destructive actions.

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 description coverage is 100%, so the schema fully documents all 7 parameters. The description adds no parameter-specific information beyond implying general management of groups with shared resources. It doesn't explain parameter interactions or usage nuances, so it meets the baseline for high schema coverage.

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 Microsoft 365 groups for team collaboration with shared resources like mailbox, calendar, and files.' It specifies the resource (M365 groups) and general action (manage), though it doesn't differentiate from sibling tools like 'manage_security_groups' or 'manage_distribution_lists' beyond mentioning shared resources.

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 mentions 'team collaboration with shared resources' but doesn't specify prerequisites, exclusions, or compare it to sibling tools like 'manage_security_groups' or 'manage_teams_policies' that might overlap in functionality.

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