Microsoft 365 Core MCP Server

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

Annotations cover read-only, idempotent, and non-destructive behavior. The description adds valuable context about the types of events analyzed (security, user activities, compliance) and the unified nature of the audit logs, which helps the agent understand the tool's scope beyond basic safety.

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, well-structured sentence that efficiently conveys purpose and scope without unnecessary words. It is front-loaded with the core functionality and includes specific domains for analysis.

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 annotations cover safety and idempotency, and the schema fully documents parameters, the description provides adequate context for a search tool. However, without an output schema, it could benefit from mentioning return format or pagination behavior to reach full completeness.

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%, with clear parameter documentation. The description does not add any additional parameter semantics beyond what the schema provides, such as OData filter examples or top limit guidance, 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 specific action ('search and analyze'), resource ('Azure AD unified audit logs'), and scope ('security events, user activities, and compliance monitoring'). It distinguishes itself from sibling tools like 'execute_graph_search' by specifying the audit log domain.

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 implies usage for security, user activity, and compliance monitoring contexts, but does not explicitly state when to use this tool versus alternatives like 'execute_graph_search' or 'generate_audit_reports'. No exclusions or prerequisites are mentioned.

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