exchange_get_message_tracking_log

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

No annotations are provided, so the description must carry the behavioral disclosure burden. 'Search' implies a read operation, and 'troubleshooting delivery' suggests intent, but the description does not disclose any behavioral traits such as result format, time window constraints, retention limits, or how filtering behaves. This is a significant gap for a diagnostic/search 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 short and avoids waste, but it is under-specified rather than genuinely concise. A single phrase with a parenthetical does not provide enough structural information for a tool with seven parameters and no annotations.

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?

With no output schema, no annotations, and a very low parameter coverage, the description needed to explain the tool's inputs, output, and search behavior. It only states the resource and purpose. This is not enough for an agent to invoke the tool correctly, especially because there are no required parameters and the semantics of the optional ones are undocumented.

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 only 14%, with a single 'ISO datetime' note on 'start'. The description itself provides no guidance on how to use start, end, sender, recipients, messageSubject, server, or resultSize, and does not clarify that all parameters are optional. The description fails to compensate for the sparse schema.

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 message tracking logs.' The parenthetical 'troubleshooting delivery' adds a clear purpose, and the resource name distinguishes it from siblings like exchange_search_admin_audit_log or exchange_test_mailflow. It doesn't explicitly differentiate from alternatives, but the object is specific enough that an agent can tell what it operates on.

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 gives a clear usage context: troubleshooting delivery. This implies when an agent should consider this tool. However, it provides no exclusions or alternatives, so it stops short of fully guiding tool selection among the many sibling tools.

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