exchange_search_admin_audit_log

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

With no annotations, the description must carry the behavioral disclosure burden. 'Search' implies a read-only operation, but the description does not explicitly state that it makes no modifications, nor does it mention default behavior, date handling, pagination, or permissions. This is insufficient for an audit-log tool.

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 compact sentence with no fluff, and the core verb+resource pair is front-loaded. It loses a point for omitting useful structure such as a parameter overview or usage note, but as a concise statement it works.

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 has four undocumented parameters, no annotations, no output schema, and a large sibling set, this one-line description is far from complete. An agent cannot determine parameter formats, defaults, return data, or constraints, making successful invocation uncertain.

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?

The input schema has four parameters with 0% description coverage, and the description does not explain startDate, endDate, userIds, or resultSize. The agent is left to infer semantics from parameter names alone, which is not enough given the schema provides no descriptions.

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 states a specific verb and resource: 'Search admin audit log', and the parenthetical '(compliance)' signals the primary use case. It is clearly distinguishable from siblings like exchange_get_message_tracking_log because the resource differs, though it does not explicitly contrast them.

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 guidance on when to use this tool versus alternatives. The word 'compliance' hints at a context but does not explain when to choose this over message tracking, mailbox queries, or other search tools.

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