Close a browser session

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description goes well beyond them: unsaved work is auto-saved as a workflow first, the reply names it, it may be an inactive draft if it would not replay, and build-bound sessions are settled or marked cancelled. This is exactly the mutation-side effect an agent could not infer from structured fields.

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?

Three dense sentences, front-loaded with the action and reason, and each clause adds real information (auto-save, discard, build-bound handling). Slightly compressed in the final sentence, but nothing is padding.

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?

No output schema exists, yet the description still explains what the reply contains (the workflow name) and how the session is finalized. For a destructive, non-idempotent-looking close operation with no annotation-level detail on data retention, this is complete.

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 coverage is 50%: discard is documented in the schema and the description reinforces it meaningfully ('Pass discard=true to close without keeping anything', default false). session_id is undocumented in both, but its meaning is unambiguous. The description adds the consequence of discard that the schema only hints at.

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 — 'Close an open browser session' — with clear scope (session is not being reused, or is being abandoned). An agent can distinguish it from session-management siblings, though no sibling is named to draw an explicit contrast.

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?

Gives concrete when-to-use conditions: task finished and no reuse intended, or abandoning a session, with the rationale that an open cloud browser keeps consuming execution time. It does not name an alternative tool for cases where the user does want to keep going, so context is clear but exclusion logic is left implicit.

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