manage_exchange_policies

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, covering the core safety profile. The description adds no behavioral context beyond what annotations provide—no mention of permissions required, rate limits, side effects, or what 'manage' entails operationally. However, it doesn't contradict annotations, so it meets the lowered bar with annotations present.

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 with zero wasted words. It front-loads the core purpose and provides specific examples without unnecessary elaboration. Every element earns its place by clarifying 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?

For a complex, destructive tool with 8 parameters, nested objects, no output schema, and many sibling alternatives, the description is inadequate. It doesn't explain what 'manage' means operationally (CRUD actions via 'action' parameter), doesn't guide usage relative to siblings, and provides no behavioral context beyond annotations. The agent would struggle to use this tool correctly without trial and error.

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 8 parameters. The description mentions policy types (mail flow rules, mobile device access, organization-wide settings) which loosely map to 'policyType' enum values, but adds no meaningful semantics beyond what the schema provides. With high schema coverage, baseline 3 is appropriate.

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 verb ('manage') and resource ('Exchange Online policies'), with specific examples of policy types (mail flow rules, mobile device access, organization-wide settings). It distinguishes from some siblings like 'manage_exchange_settings' by focusing on policies rather than general settings, though it doesn't explicitly differentiate from all policy-related tools like 'manage_dlp_policies'.

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, appropriate contexts, or exclusions. With many sibling tools managing different aspects of Microsoft 365 policies (e.g., 'manage_dlp_policies', 'manage_conditional_access_policies'), the agent receives no help in selecting the right tool for Exchange policy management.

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