m365_list_transport_rules

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

With no annotations, the description carries the full behavioral burden, and it only implies a read-only listing via the verb 'Lists'. It says nothing about permissions required, pagination or result volume, or whether the filter is applied server-side, all of which matter for a tenant-wide directory listing.

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?

A single front-loaded sentence with no filler or repetition; the scope qualifier sits before the resource. It is efficient, though it is arguably too terse to carry any of the usage or parameter context the tool needs.

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?

An output schema exists, so return values need not be explained, but the description leaves the one parameter undefined, offers no usage guidance, and provides no behavioral context in the absence of annotations. For a compliance-relevant tenant-wide listing tool, this is thin.

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 single parameter filter_state is undocumented in both schema and description. The description gives no hint about what states can be filtered on or the accepted value format, so it fails to compensate for the coverage gap.

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 names a specific verb ('Lists'), a specific resource ('transport rules') and a scope ('tenant-wide mail flow ... in Exchange Online'), which is enough to separate it from the mailbox-scoped m365_list_inbox_rules sibling without opening either schema. It does not, however, explicitly name that sibling, so the differentiation is left implicit.

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 phrase 'tenant-wide' hints at the scope, but there is no explicit when-to-use statement, no mention of when this is preferable to m365_list_inbox_rules, and no prerequisites or auth context. An agent has to infer applicability purely from the resource name.

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