status

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

readOnlyHint=true already tells the agent this is a safe, non-mutating probe, and the description usefully enumerates the four readiness states it inspects. However, with no output schema it doesn't say what a not-ready result looks like (false vs. thrown error vs. status object), which is exactly the information an agent needs to act on the result.

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, and the conditions are listed in the order an agent would care about them (reachable, then tab state, then pairing).

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 zero-parameter read-only probe with annotations covering the safety profile, the description covers what is checked. The one missing piece is outcome shape on failure, since no output schema exists to document it.

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?

Zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no inputs are needed.

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 supplies a specific verb ('check') and a concrete set of conditions being verified: chromefile reachability, tab open, paired, and ready. This clearly separates it from the sibling tools, which all operate on conversations/messages rather than connection health, though the bare name 'status' alone would have been 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?

Usage is only implied: a readiness check naturally precedes list_conversations, read_messages, or send_message, but the description never says so or names an alternative. There are no explicit when-not conditions (e.g., whether it should be called before every operation or only after failures).

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