manage_conditional_access_policies

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

Annotations indicate this is a destructive, non-idempotent, mutable tool. The description adds value by specifying the resource type (Azure AD conditional access policies) and examples of controls (MFA, device compliance, location-based), which helps the agent understand what might be affected. However, it doesn't disclose critical behavioral details like authentication requirements, rate limits, or what 'destructive' specifically entails (e.g., policy deletion impacts).

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 words and directly states what the tool does. However, it could be slightly more structured by separating the purpose from the examples 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?

Given the tool's high complexity (8 parameters with nested objects, destructive hint), no output schema, and rich annotations, the description is somewhat incomplete. It covers the 'what' but lacks guidance on 'how' to use it effectively, error handling, or result interpretation. The annotations help, but for a tool with significant destructive potential, more context 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?

Schema description coverage is 100%, so parameters are fully documented in the schema. The description adds minimal semantic context by mentioning 'MFA, device compliance, and location-based controls,' which loosely maps to grantControls.builtInControls and conditions.locations, but doesn't explain parameter relationships or usage patterns. This 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 Azure AD conditional access policies' with specific examples of what can be managed (MFA, device compliance, location-based controls). It uses the verb 'manage' which aligns with the multi-action capability indicated by the action parameter. However, it doesn't explicitly differentiate from sibling tools like 'manage_authentication_strengths' or 'manage_defender_policies' which might handle related security controls.

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 'zero-trust security' context but doesn't specify prerequisites, appropriate scenarios, or exclusions. With many sibling tools for managing security policies (e.g., manage_defender_policies, manage_exchange_policies), the agent receives no help in choosing between them.

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