m365_add_sender_to_allow_list

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

With no annotations provided, the description carries the full behavioral burden and largely fails: it says nothing about required permissions, whether the entry overwrites an existing allow-list rule, how the expiration is set or renewed, or what happens if the sender is already listed. The only extra signal is the generic 'with an expiration period' phrase.

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. It earns its brevity, though the brevity is partly the source of the missing behavioral detail rather than a virtue of precision.

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, but for a security-sensitive mutation with zero annotations and zero schema descriptions, the definition should cover permissions, idempotency, and the unexplained expiration behavior. The dangling 'expiration period' reference is left unresolved.

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 coverage is 0%, so the description must compensate and does not. It loosely matches 'sender_or_domain' but gives no format guidance (bare address vs domain vs wildcard), and it never mentions the 'note' parameter. Worse, it references an 'expiration period' that does not exist as a parameter, creating ambiguity about how that value is supplied.

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 ('Adds a sender email or domain to the Tenant Allow List'), and the expiration qualifier narrows the behavior. It is clearly distinguishable from the sibling m365_list_tenant_allow_list, though it never names that sibling or other alternates.

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 or when-not-to-use guidance, no mention of prerequisites (e.g. mail-flow or spam-filtering context), and no pointer to the related list tool or removal flow. An agent must infer the usage context entirely from the name.

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