exchange_list_mailbox_databases

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states a read-only listing action and does not mention scope, pagination, what the includePreExchange2013 flag affects, or any other behavioral characteristics.

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 extremely concise and front-loaded, with no filler words. However, it is under-specified to the point of being terse: it omits parameter meaning and usage context, so the brevity is not fully effective.

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?

For a simple one-parameter listing tool, the description is incomplete. It does not explain the optional includePreExchange2013 parameter, the expected output, or when to select this tool over related siblings. With no output schema, the description should have provided more context.

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 0% and the description does not explain the only parameter, includePreExchange2013. The parameter name hints at including pre-Exchange 2013 databases, but its effect, default value, and usage are entirely undocumented.

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 'List mailbox databases' uses a specific verb and resource, clearly indicating a collection-level listing operation. It does not explicitly differentiate from the sibling exchange_get_mailbox_database, but the plural 'databases' versus singular sibling names provides a reasonable distinction.

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 such as exchange_get_mailbox_database or exchange_get_database_copy_status. There are no stated conditions, exclusions, or recommended use cases.

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