m365_set_group_external_delivery

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

No annotations are provided, so the description carries the full behavioral burden. It does clarify the security-relevant meaning of the toggle (accepting messages from unauthenticated external senders), which is genuine context beyond the raw schema, but it omits permission requirements, reversibility, and the effect of applying the change.

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?

A single front-loaded sentence with no filler; the setting and its scope appear immediately. Nothing is redundant.

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?

An output schema exists, so return values need not be explained, and the tool is small (2 params). However, for a mutation of a security-sensitive setting with no annotations, the description should at least mention the default and identity format; as written it is minimally adequate.

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 0%, so the description must compensate. It implicitly explains what allow_external controls, but never names either parameter, does not state the default (allow_external defaults to true), and gives no format guidance for group_identity (name vs SMTP vs GUID).

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 names a specific verb (Configures) and a precise resource/setting (whether a distribution group accepts messages from unauthenticated external senders), which clearly separates it from sibling group tools like m365_manage_group_member and m365_list_distribution_groups. It stops short of explicitly naming an alternative or contrasting tool, so it is clear but not fully differentiated.

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?

There is no when-to-use guidance, no stated prerequisites (e.g., required admin role for external-delivery changes), and no reference to related tools such as m365_list_distribution_groups or transport-rule tools. The agent must infer the context entirely.

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