list_m365_accounts

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

With no annotations, the description carries the behavioral burden. It implies a read-only list operation scoped to accounts connected on the local computer and discloses some returned fields, but it does not state permissions, pagination behavior, or what happens when no accounts are connected. The trailing incomplete clause reduces the clarity of the disclosure.

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 definition is short and front-loads the purpose, but it ends with an incomplete clause ('which one is the...') that appears accidentally truncated. It is concise, but the broken sentence weakens structure.

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 zero-parameter list tool with no output schema, the description should at least fully explain what is returned and how it differs from related list tools. It partially enumerates return fields and local scope, but it is incomplete and does not guide selection among similar account-listing siblings.

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 tool has zero parameters and the schema description coverage is 100%, so there are no parameter semantics to explain. Per the rubric, zero parameters establish a baseline of 4.

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: list Microsoft 365 accounts connected on this computer, and names returned fields like email (upn), id, and display name. It does not, however, distinguish this tool from sibling account-listing tools such as list_accounts, list_email_accounts, or outlook_list_accounts, and the sentence is truncated.

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 no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The agent can infer it is for listing M365 accounts, but sibling tools with overlapping account-listing purposes are not addressed.

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