outlook_bulk_list

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

No annotations are provided, so the description carries the full behavioral burden. It reveals that virtualization is bypassed and that conversation-IDs plus a preview are returned, but says nothing about read-only safety, pagination semantics of maxScrolls, cost of full enumeration, or permissions.

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?

Two compact sentences, front-loaded with purpose and the virtualization caveat, followed by return contents. Nothing is redundant, though the tool name and description carry some overlap.

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 annotations and no output schema, the description should explain return shape, enumeration limits, and safe usage. It only partially covers returns (conversation-IDs + preview) and omits pagination behavior and the consequence of maxScrolls, so it is incomplete for the agent.

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%: folder's accepted values and maxScrolls' default of 140 are already documented in the schema. The description adds no syntax or format details beyond that, so it earns only the baseline.

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?

States a specific verb and resource: it lists all emails in a folder and explicitly notes it overcomes message-list virtualization, which distinguishes it from siblings like outlook_list_recent. However, it never names those siblings, so an agent must infer which of the ten other tools it replaces.

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?

No when-to-use or when-not-to-use guidance. It does not contrast with outlook_list_recent or outlook_search, which are the obvious alternatives for listing or finding mail, leaving the agent to guess when scroll enumeration is preferable.

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