outlook_close

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, and it discloses nothing beyond the act of closing. It does not say whether the session/login is discarded, whether in-flight operations are aborted, whether a subsequent tool call relaunches the browser, or whether the call is idempotent if no instance is running.

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 short sentence with the action front-loaded and no filler. Nothing in it is redundant.

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 lifecycle/teardown tool inside a suite of browser-backed outlook_* tools, the description omits the consequences an agent most needs: loss of session state, impact on other tools, and whether re-login is required afterwards. With no annotations and no output schema to fall back on, these gaps are unmitigated.

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 takes zero parameters, so there is nothing for the description to clarify beyond the schema. Baseline 4 applies for a parameterless tool.

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 and resource ('Schließt die Hintergrund-Browserinstanz'), so an agent immediately knows this tears down the background browser. It does not differentiate itself from any sibling, but no sibling performs teardown, so the gap is minor.

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?

There is no explicit statement of when to call this versus keeping the browser alive, nor any prerequisite or sequencing guidance. Use is only weakly implied by the name and by the fact that other outlook_* tools need the browser instance.

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