browser_status

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

No annotations are provided, so the description carries the full burden. It does disclose the return content (share state, URL, title), which is valuable given there is no output schema, but it says nothing about side effects, whether the browser must already be open, or what an unshared/absent result looks like.

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 tight sentence with no filler, and the key payload (share state, URL, title) is stated up front. It is appropriately sized for a zero-argument status check.

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?

With no output schema, the description does the minimum by listing the returned fields, and for a trivial 0-param status query that is close to sufficient. It still omits the conditions under which a tab is considered 'shared' and what the agent should do with the result, so it is adequate but not 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter-level gaps exist.

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 the resource (VS Code integrated-browser tab) and the information returned (shared status, URL, title), so an agent can infer it is a state query. However, it is phrased as a noun clause rather than a verb+resource action, and it never contrasts itself with the closely related browser_tabs sibling, leaving the boundary ambiguous.

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 statement of when to call this versus browser_tabs, browser_snapshot, or any other sibling, and no prerequisites or exclusions. The agent must infer usage entirely from the name and the returned-data clause.

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